Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘈𝘤𝘩𝘰𝘴 𝘪𝘯𝘧𝘰| 𝘪𝘳𝘭 𝘭𝘰𝘭𝘭𝘪𝘱𝘰𝘱!

Channel

𝘈𝘤𝘩𝘰𝘴 𝘪𝘯𝘧𝘰| 𝘪𝘳𝘭 𝘭𝘰𝘭𝘭𝘪𝘱𝘰𝘱!

@achosIrlLollipop

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

165subscribers

+86 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1004403247660
TypeChannel
Username@achosIrlLollipop
CreatedBetween 1 June 2026 and 1 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/achosIrlLollipop

Previous handles

@achosIrlLollipop was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@MikuAchosCanon
held 13 August 202613 August 2026

Growth

79168123.513 August 2026 — 79 subscribers14 August 2026 — 80 subscribers2 September 2026 — 168 subscribers2 September 2026 — 168 subscribers11 September 2026 — 165 subscribers16513 August 202611 September 2026
5 measurements spanning 29 days, net +86. 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 66–181 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 19:38165-3
2 Sept 2026, 03:45168no change
2 Sept 2026, 03:30168+88
14 Aug 2026, 13:4780+1
13 Aug 2026, 17:1679first reading

Engagement

33 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.0%
avg views ÷ 165 subscribers
Avg views / post
95.7
14 posts measured
Reaction rate
3.46%
reactions ÷ views · ER floor
Posts in window
14
of 33 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 5 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 August 2026
Posts held33 (1 August 202631 August 2026)
Views total1,340
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 03:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

446 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 19.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54269401148005157538819.7%
custom 54272664979552787338719.5%
custom 52605482585051920258118.2%
custom 54251309843811303607115.9%
custom 54066796631435956956113.7%
custom 54270847478242086665813.0%

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 17 of the 33 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 446 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 33 most recent posts we hold, published 1 August 2026 to 31 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.

Recent posts

31 Aug 2026, 20:22 UTC36 viewsread 2 September 2026

Кинтте мне буст ради бога.🥺🥺🥺

31 Aug 2026, 19:29 UTC42 views7 reactionsread 2 September 2026
Photo

🔠🔠🔠🔠 🔠🔠➖Favorites.. 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Нерико. 🐇🫐🫐😀😀 маня. 🫐🫐🌼Ани.🫐🫐🫐Форк. 🌟🌟 🤩🤩Андрей.➖Саня.🤩🤩 🤩киттиз. ➖➖➖➖➖➖➖➖➖➖➖➖

custom 54269401148005157533custom 54272664979552787332custom 54251309843811303601custom 54270847478242086661

31 Aug 2026, 19:12 UTC46 views3 reactionsread 2 September 2026

Любимки, скиньте своих лаф персонажей и прем эмодзи с ними + ссылку на свой инфо. 👾👾

custom 54269401148005157532custom 54272664979552787331

31 Aug 2026, 18:47 UTC51 views1 reactionsread 2 September 2026

Мне так обидно, что я стараюсь у всех активить, но у меня активит только таракан и Киркоров покойся с миром.

custom 54272664979552787331

31 Aug 2026, 17:40 UTC306 views3 reactionsread 2 September 2026
Photo

Уже делала, ну ладно.

custom 54251309843811303601custom 54270847478242086661custom 54272664979552787331

31 Aug 2026, 09:24 UTC46 viewsread 2 September 2026
Forwarded from @scarashunPhoto

Photo, posted without a caption

28 Aug 2026, 11:25 UTC77 viewsread 2 September 2026
Forwarded from @loretta0w0

​​🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩 ❤️❤️❤️❤️❤️❤️❤️❤️❕🤩 🗝т лоретты в честь 1к пдп 🗯 🗯 𝟏 место🥹нфт 🤩🤩🤩 🗯 𝟐 место🥹нфт 🤩🤩💌 🎀𝟑 место🥹 нфт 🤩🤩 🎀𝟒 место😻 нфт 🗯🤩🤩 🤩𝟓-𝟖 место🥹подарок на 15 зв🤩🤩 🤩 𝟗-𝟏𝟎 место🥹10 зв в канал 🗯 🎀🎀🤩🤩 ᥡᥴловᥙя 🤩🤩 🤩 подписɑׁться на этот инфᨵ⁠⁠⁠ без дальнейшей отписки. 🤩 ℘т в свой инфꪮ (10+) нꫀ⁠⁠⁠⁠ стикером. 🤩 𝓓ꪮки в коммы с пꪮрядковым нᨵ⁠⁠⁠мꫀ⁠⁠⁠ром. отписка/нет рт - мгновенное аннулирование. итоги 4 сентября в 19:

Showing the 12 most recent of 33 posts we hold for @achosIrlLollipop. 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.

Forward network

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.

Mentions

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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“𝘈𝘤𝘩𝘰𝘴 𝘪𝘯𝘧𝘰| 𝘪𝘳𝘭 𝘭𝘰𝘭𝘭𝘪𝘱𝘰𝘱!” (@achosIrlLollipop), 165 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/achosIrlLollipop.

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.