Sajna Ve Sajna Ve

The song Sajna Ve Sajna Ve by Altamash Faridi, Shadab Faridi has been played 101,601 times on Spotify since its release on October 03, 2013.

Other songs from Altamash Faridi, Shadab Faridi

Dil Mera Muft Ka

Pritam, Nandini Srikar, Muazzam, Rizwan, Shadab Faridi, Altamash Faridi, Shabab Sabri
Tere Vaaste - Jhankar Beats

Varun Jain, Sachin-Jigar, Shadab Faridi, Altamash Faridi, Amitabh Bhattacharya, Hero And King Of Jhankar Studio
Bollywood New Year Party Non-Stop Remix

Kanika Kapoor, Amar Jalal, IP Singh, Yohani, Harjot Kaur, Arijit Singh, Nikhita Gandhi, Diljit Dosanjh, Charan, Zahrah S Khan, Altamash Faridi, Yo Yo Honey Singh, Neha Kakkar, Sachet Tandon, Parampara Tandon, KiDi, Tulsi Kumar, Guru Randhawa, Neeraj Shridhar, Sunidhi Chauhan, Kedrock, Sd Style
Tumse Mohabbat

Altamash Faridi, Aakritti Mehra, S.R.Dehariya, Muskan Bamne, Rohan Mehra
Tu Meri Main Tera (feat. Shadab Faridi & Altamash Faridi)

Mannan Shaah, Rahat Fateh Ali Khan, Shadab Faridi, Altamash Faridi

Frequently asked questions

: Due to Spotify's policy of not publicly sharing daily stream counts, our system independently records this data on a daily basis for millions of tracks. Given the vast number of tracks we monitor, there may be occasions where certain tracks are not processed on specific days, leading to missing data points. Rest assured, we continuously work to minimize these gaps and provide comprehensive coverage.
: There are two primary reasons you might notice irregularities in the data points:

- Inconsistent Stream Counts for a Day: Sometimes, a data point may represent the stream count for two days instead of one. This inconsistency arises because Spotify does not update its public stream count at a fixed time daily. If our data recording aligns with these fluctuations, it can lead to inaccuracies.
- Anomalous Data Points (including negative streams): On occasion, you might observe highly irregular data points, such as negative daily streams. These are typically the result of metadata discrepancies on Spotify's end, like different tracks sharing the same International Standard Recording Code (ISRC). In such cases, reaching out to us can be very helpful. We can often disregard these erroneous data points to present a more accurate graph.

In both situations, we're committed to continuously improving our data accuracy and are here to assist with any specific concerns you might have.
: The extent of our historical data varies depending on the track. For some tracks, our records go as far back as September 2023. However, there are tracks for which we may not have any historical data yet. But here's the good news: once you look up a specific track on our system, you activate our tracking for that track. From that point forward, we will diligently record its data daily, ensuring you have continuous and up-to-date insights from the moment you start using our service.
: Currently, our platform does not provide a direct option to export data. However, we understand the importance of this feature, and we're excited to announce that a CSV export functionality is on our roadmap and will be introduced soon. For developers seeking more integrated solutions, we offer an API service available on Rapid API. If you need larger volume or a dedicated solution, please contact us.
: This occurs due to Spotify's policy of only displaying public stream counts for tracks that have surpassed 1,000 streams. Consequently, if you see a stream count marked as 0 in our system, it indicates that the total stream count for that track is currently below 1,000. As the track accumulates more streams and crosses this threshold, the accurate stream count will start being reflected in our data.