Me
custom 54138247234925704816custom 54135621764367331654custom 54137852570380907394custom 52581347832375778243custom 52582680646627041692custom 54384175816754118002custom 54133346333643577901custom 54206218957855401951

Channel
@iviiiice
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
108subscribers
+15 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002400212102 |
|---|---|
| Type | Channel |
| Username | @iviiiice |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/iviiiice |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 23:01 | 108 | +5 |
| 8 Sept 2026, 10:36 | 103 | +9 |
| 30 Aug 2026, 22:02 | 94 | +1 |
| 24 Aug 2026, 17:34 | 93 | -1 |
| 17 Aug 2026, 12:39 | 94 | +1 |
| 10 Aug 2026, 17:02 | 93 | no change |
| 10 Aug 2026, 10:46 | 93 | first reading |
10 posts held, back to 11 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 10 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
402 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 20.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5413334633364357790 | 84 | 20.9% | |
| custom 5438417581675411800 | 52 | 12.9% | |
| custom 5413824723492570481 | 51 | 12.7% | |
| custom 5440697032488553111 | 51 | 12.7% | |
| custom 5413785257038090739 | 45 | 11.2% | |
| custom 5413562176436733165 | 43 | 10.7% | |
| custom 5258134783237577824 | 34 | 8.46% | |
| custom 5420621895785540195 | 25 | 6.22% | |
| custom 5413370616600363190 | 12 | 2.99% | |
| custom 5258268064662704169 | 5 | 1.24% |
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 10 of the 10 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 402 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 11 April 2026 to 1 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 @iviiiice. 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 10 most recent posts we hold for this entry, published 11 April 2026 to 1 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.
Me
custom 54138247234925704816custom 54135621764367331654custom 54137852570380907394custom 52581347832375778243custom 52582680646627041692custom 54384175816754118002custom 54133346333643577901custom 54206218957855401951
Photo, posted without a caption
custom 541382472349257048114custom 54384175816754118008custom 54133346333643577907custom 52581347832375778245custom 54206218957855401952custom 52582680646627041691custom 54133706166003631901custom 54135621764367331651
Photo, posted without a caption
custom 525813478323757782417custom 541333463336435779011custom 54135621764367331659custom 54137852570380907393custom 54206218957855401952custom 54384175816754118002custom 52582680646627041691custom 54133706166003631901
Photo, posted without a caption
custom 542062189578554019510custom 54133706166003631907custom 52581347832375778245custom 54406970324885531114custom 54133346333643577902custom 54384175816754118002custom 52582680646627041691custom 54135621764367331651
Photo, posted without a caption
custom 541356217643673316514custom 54384175816754118009custom 54133346333643577908custom 52581347832375778244custom 54406970324885531112custom 54133706166003631901custom 54138247234925704811custom 54206218957855401951
Photo, posted without a caption
custom 541333463336435779016custom 54138247234925704817custom 54384175816754118006custom 54206218957855401955custom 54406970324885531113custom 54137852570380907392
Photo, posted without a caption
custom 541378525703809073925custom 544069703248855311112custom 54384175816754118006custom 54133346333643577903custom 54135621764367331653custom 54138247234925704812custom 54206218957855401952
Photo, posted without a caption
custom 541333463336435779018custom 544069703248855311112custom 54138247234925704819custom 54133706166003631902custom 54206218957855401952custom 54135621764367331651custom 54384175816754118001
Video, posted without a caption
custom 541382472349257048110custom 54406970324885531117custom 54384175816754118006custom 54135621764367331655custom 54137852570380907395custom 54133346333643577902
Photo, posted without a caption
custom 541333463336435779016custom 543841758167541180010custom 54406970324885531118custom 54135621764367331655custom 54137852570380907395
Showing the 10 most recent of 10 posts we hold for @iviiiice. 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“@iviiiice” (@iviiiice), 108 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/iviiiice.
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.