Posted without readable text
custom 54452752442877978239custom 53417479953753450184custom 53395379168739750273custom 52355891641660323241

Channel
@niterisee
On this record: Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry
87subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002635651825 |
|---|---|
| Type | Channel |
| Username | @niterisee |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 5 September 2026 |
| On Telegram | t.me/niterisee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 07:53 | 87 | +1 |
| 22 Aug 2026, 10:22 | 86 | +1 |
| 15 Aug 2026, 05:57 | 85 | +1 |
| 9 Aug 2026, 17:15 | 84 | no change |
| 7 Aug 2026, 00:33 | 84 | first reading |
20 posts held, back to 21 April 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
233 reactions across 16 posts, in 23 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235589164166032324 | 50 | 21.5% | |
| custom 5233670739713861453 | 44 | 18.9% | |
| custom 5467913050537363967 | 16 | 6.87% | |
| custom 5399827803032026505 | 15 | 6.44% | |
| custom 5445275244287797823 | 14 | 6.01% | |
| custom 5226469552732279877 | 11 | 4.72% | |
| custom 5397636021091343911 | 11 | 4.72% | |
| custom 5341747995375345018 | 9 | 3.86% | |
| custom 5395786664008260070 | 9 | 3.86% | |
| custom 5467733761422561355 | 9 | 3.86% | |
| custom 5371092427417351475 | 8 | 3.43% | |
| custom 5364095517670276759 | 6 | 2.58% | |
| custom 5395403617349965418 | 5 | 2.15% | |
| custom 5280697702437393459 | 4 | 1.72% | |
| custom 5339537916873975027 | 4 | 1.72% | |
| custom 5397968455855019376 | 4 | 1.72% | |
| custom 5460708827013879029 | 4 | 1.72% | |
| custom 5280738448792133241 | 3 | 1.29% | |
| custom 5235650238600993674 | 2 | 0.858% | |
| custom 5397973193203926548 | 2 | 0.858% | |
| 3 further kinds | 3 | 1.29% |
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 16 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 233 reactions 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 21 April 2026 to 6 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @niterisee. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 21 April 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Posted without readable text
custom 54452752442877978239custom 53417479953753450184custom 53395379168739750273custom 52355891641660323241
Posted without readable text
custom 523558916416603232411custom 54452752442877978235custom 53417479953753450183
Posted without readable text
custom 53957866640082600707custom 52355891641660323241custom 53413773654675052711
˖ [ ПЕРЕДАЧА ЭСТАФЕТЫ ОТ ЛИРЫ ] ˖ ◤ ───────────────────── ❔ » Суть эстафеты: нужно упомянуть и написать, что бы ты сделал с человеком, передавшим тебе эстафету. ˖ [ МОЙ ОТВЕТ… ] ˖ 🛌 » …Я мягко возьму тебя за руку, и отведу в наш шатер из одеял. Там, под уютным светом фонарика, я напою тебя горячим какао, укутаю пледом и сяду напротив, слушая, как прошёл твой день…🦋 ˖ ࣪ ⊹ ◤ ───────────────────── ˖ [ ПЕРЕДАЮ… ] ˖ Он…
custom 52355891641660323246custom 53395379168739750271custom 53417479953753450181custom 54677337614225613551
File, posted without a caption
custom 52355891641660323242custom 53954036173499654182custom 54677337614225613552custom 53417479953753450181
• °.⊹ ࣪ ˖〔 . ❌ . 〕˖ ࣪ ⊹.° • ◤ ────────────────── — Я просто хочу помочь тебе… — …Я знаю.
custom 53710924274173514758custom 53640955176702767594custom 52807384487921332412custom 53979731932039265482custom 52355891641660323241
Channel name was changed to «❕//: ❮ ɴɪᴛᴇ⬦ʀɪsᴇ ❯ « ☁️»
Posted without readable text
🥹 » …Теперь какое-то время я буду зелёненькой ⚪ ˖ ࣪ ⊹ P.S.: Скажем так: летний ивент длиной в лето 🥹
custom 52264695527322798774custom 52336707397138614531custom 52806977024373934591custom 54048073580502292881custom 54677337614225613551
Channel photo updated
❔ » Как думаете, дропнуть ли это в спирит? Ну так, чисто по приколу? ˖ ࣪ ⊹
custom 52264695527322798777⚡1custom 52806977024373934591
• °.⊹ ࣪ ˖ 〔 🍀 〕 ˖ ࣪ ⊹.° • ◤ ───────────────────── ⚪ » Юююху! ˖ ࣪ ⊹ . ⚪ » Последний экзамен сдан (наконец-то). Сессия успешно окончена. И сейчас я хочу поделиться с вами мини-стори, которая сделала мой день: . ◤ ───────────────────── ⚪ » Сегодня была пересдача экза (мы до этого уже писали). Лично я тогда писала контрольную, ведь без нее меня не допустят, а я так и не сдала ей эти гребаные интегралы. Я морально готов…
custom 52355891641660323248custom 53954036173499654182custom 54679130505373639672custom 52336707397138614531custom 52806977024373934591
Showing the 12 most recent of 20 posts we hold for @niterisee. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
[ ⚠️ » ВНИМАНИЕ ВОПРОС ] ◤ ───────────────────── …Хотите ли вы, чтобы я сделала ~ЩитПост?~ 🌙 ˖ ࣪ ⊹ ❌ » Он будет создан как отдельный закрытый канал, где я буду выкладывать всякую фигню, не засоряя основной ТГК 👩🎓 😀 » Что думаете? Делаем? �
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 21 April 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“❕//: ❮ ɴɪᴛᴇ⬦ʀɪsᴇ ❯ « ☁️” (@niterisee), 87 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/niterisee.
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.