Telegram RegisterThe public register of Telegram

Channel

Now Playing [logs]

@nowplaylogs

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

329subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001357569996
TypeChannel
Username@nowplaylogs
DescriptionNews about @nowplaybot Contact (EN/RU): @anna_ignores Donate: paypal.me/koteeq or @donateanna
Created11 May 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/nowplaylogs

Growth

3296 Aug 2026, 03:23 — 329 subscribers6 Aug 2026, 21:47 — 329 subscribers6 Aug 2026, 03:236 Aug 2026, 21:47
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 328–330 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 21:47329no change
6 Aug 2026, 03:23329first reading

Engagement

20 posts held, back to 10 June 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 29 February 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Links
4

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

577 reactions across 9 posts, in 15 distinct kinds. The most used accounts for 39.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢22639.2%
16829.1%
🔥9115.8%
👍152.60%
🙏152.60%
🥰132.25%
🥱132.25%
😁101.73%
🌭81.39%
❤‍🔥40.693%
👌40.693%
🤣40.693%
🌚30.52%
🤔20.347%
👏10.173%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 577reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 10 June 2020 to 29 February 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

29 Feb 2024, 13:51 UTC≈8,250 views333 reactionsread 6 August 2026

tl;dr на русском: бот сломался, я попробовала быстро его починить, но код древний и всратый, поэтому ничего не получилось. проекту нужно больше времени, сил и внимания, чтобы починить эту и другие накопившиеся проблемы. я немножко овощ, так что этих ресурсов у меня сейчас нет. релизить бота в опенсорс я не буду, потому что код говно и мне за него стыдно (не спорьте со мной об этом, пожалуйста). постараюсь починить к

😢149🔥9156🙏10😁9🌭5🤣4🌚3

29 Feb 2024, 13:48 UTC≈8,190 views117 reactionsread 6 August 2026

so umm.... the bot is broken, yea. spotify suddenly changed their api responses format, so my bot can't parse them anymore. i tried quickly patching thta up, but the code is so old and janky, i failed. it's not the only issue with this project, there are more: - unstable downloader (often, the audio file wouldn't load, showing an error instead) - some yandex music auth issues?? idk i never use yandex music, but peop

86😢15🥱11❤‍🔥4😁1

9 Aug 2022, 20:28 UTC≈9,110 views108 reactionsread 6 August 2026

Yandex.Music users might experience problems, but I don’t have any time to look into this as I’m very busy with my full-time job :( I will try my best to find spare time and investigate this. For now I strongly recommend using Spotify as it’s mostly stable on @nowplaybot. ❤️

😢6221👍11🙏5👌4🌭3🥱2

12 Mar 2021, 01:07 UTC≈11,500 views11 reactionsread 6 August 2026

New: You can send a vibing cat 🐱 gif to your friend by typing "@nowplaybot cat". The cat will vibe to the track you're listening. Works with Spotify only. The BPM of the track is obtained from Spotify API, so I'm not responsible for any wrong vibes, you know.

🥰11

19 Aug 2020, 14:44 UTC≈10,700 views2 reactionsread 6 August 2026
Photo

The problem was connected to Spotify outage somehow. Looks like it’s fixed by its own now.

2

19 Aug 2020, 06:33 UTC≈7,950 views0 reactionsread 6 August 2026

⚠️ There are some outage reports but I have no idea what’s wrong, the bot works fine for me. Investigating.

8 Aug 2020, 12:06 UTC≈6,810 viewsread 6 August 2026

Have you also seen that "no MD5 hash blah-blah" error? Don't tell anyone then. 🤐 I've already fixed that!

22 Jul 2020, 23:26 UTC≈6,590 views2 reactionsread 6 August 2026

New: Fixed "this song is not available :(" error for tracks that are not available on Deezer. The bot will try to download such tracks directly from Spotify It's VERY slow. It slowly downloads from Spotify in a single thread, then it converts the song from ogg to mp3 with ffmpeg. 🐢, but works. Fun fact: 163 users got this error 302 times overall.

2

17 Jul 2020, 21:48 UTC≈5,400 viewsread 6 August 2026

The bot is down. Same as many other services. Cloudflare and Google DNS are experiencing major outage right now. I'm sorry :c UPD: It's up!

12 Jul 2020, 21:59 UTC≈4,960 viewsread 6 August 2026

New: Last.fm is available as an experimental source alternative to Spotify/Yandex.Music. Please note that the matching is fuzzy cause it's based on artist name and song title. I warned you. Read the story in Russian. Use /logout if you had your Spotify/Yandex.Music account linked and want to switch to Last.fm

11 Jul 2020, 11:24 UTC≈4,980 views1 reactionsread 6 August 2026

New bot userpic made by @alberry_art! 🎉

1

Showing the 12 most recent of 20 posts we hold for @nowplaylogs. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 975,448 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 August 2026 — this entry's latest reading, not the date you are reading this.

“Now Playing [logs]” (@nowplaylogs), 329 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/nowplaylogs.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.