Channel
@selena_nightroll
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
254subscribers
+3 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001531434805 |
|---|---|
| Type | Channel |
| Username | @selena_nightroll |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/selena_nightroll |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 10:57 | 254 | +5 |
| 6 Sept 2026, 23:57 | 249 | -1 |
| 30 Aug 2026, 08:34 | 250 | -1 |
| 14 Aug 2026, 07:30 | 251 | no change |
| 14 Aug 2026, 07:18 | 251 | first reading |
12 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 12 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
281 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 37.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5458667124115408588 | 105 | 37.4% | |
| custom 5438472179299683063 | 45 | 16.0% | |
| custom 5438609897426029077 | 39 | 13.9% | |
| custom 5454207908680078563 | 33 | 11.7% | |
| custom 5368578110612596893 | 22 | 7.83% | |
| custom 5233702896134029167 | 13 | 4.63% | |
| custom 5343588320142205900 | 11 | 3.91% | |
| custom 5832186634413546956 | 9 | 3.20% | |
| custom 5344015892726457307 | 3 | 1.07% | |
| custom 5280984954145118088 | 1 | 0.356% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 12 of the 12 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 281 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 30 July 2026 to 13 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
☺️сем привет, сегодня у меня день рождения и по традиции, я была бы рада репосту моих работ в качестве подарка!💘 мне исполнилось целых 12 лет, ну только если циферки чуть чуть местами поменять хехе 🌟🌟🌟 @sadyuchii @sadyuchii @sadyuchii
custom 54542079086800785635
Кто хочет со мной встречаться пиши я
custom 523370289613402916713custom 54386098974260290774custom 54586671241154085883
Я и падпищеки
custom 545420790868007856320custom 54586671241154085886custom 54386098974260290773
Photo, posted without a caption
custom 545866712411540858821
❤️🩹❤️🩹❤️🩹
custom 545866712411540858810custom 54386098974260290773custom 58321866344135469563custom 52809849541451180881
У меня уже заказали коммишку па некси будет ваще круто имбо 🗣️🗣️🗣️
custom 543860989742602907716custom 54384721792996830637custom 54586671241154085885
Все дороги ведут к некса найц
custom 545866712411540858814
Я хачу рисовать некса найц фанарт
custom 545866712411540858814custom 54384721792996830634custom 58321866344135469561
наконец-то закончила. Попробовала другой покрас вместе с лайном на одном фоне, поэтому мне так больше нравится. #арт #roblox #forsaken
custom 543847217929968306316custom 545866712411540858810custom 54542079086800785636
Я щас не у себя в городе а в гостях живу поэтому через из мира выпадаю постоянно даже в щп ниче не пишу но я живая
custom 543847217929968306318custom 54386098974260290778custom 54586671241154085887custom 53440158927264573071
Нифига жесть Моя брошк старалась над видосиком долга очень поэтому поддержите 🤩
custom 54586671241154085888custom 54386098974260290774custom 58321866344135469564
#forsaken #традишка Тутойм
custom 536857811061259689322custom 534358832014220590011custom 54586671241154085887custom 53440158927264573072custom 54542079086800785632custom 54386098974260290771custom 58321866344135469561
Showing the 12 most recent of 12 posts we hold for @selena_nightroll. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“‧₊˚ೃ селёдка𓈒⊹ꮺ˚” (@selena_nightroll), 254 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/selena_nightroll.
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.