💐
custom 52604809649575804065custom 52581234788836527114custom 54543530528048620594

Channel
@tgquasiiik
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
56subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002088504811 |
|---|---|
| Type | Channel |
| Username | @tgquasiiik |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/tgquasiiik |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 03:54 | 56 | +1 |
| 10 Aug 2026, 08:16 | 55 | no change |
| 7 Aug 2026, 18:48 | 55 | first reading |
9 posts held, back to 12 July 2025 — 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 9 posts for this entry, the most recent from 8 March 2026. An engagement rate over an empty window would be a number about nothing.
181 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 24.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5260480964957580406 | 45 | 24.9% | |
| custom 5258123478883652711 | 41 | 22.7% | |
| custom 5285419864360498767 | 41 | 22.7% | |
| custom 5411415075040806885 | 29 | 16.0% | |
| custom 5454353052804862059 | 25 | 13.8% |
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 9 of the 9 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 181 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 12 July 2025 to 8 March 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.
💐
custom 52604809649575804065custom 52581234788836527114custom 54543530528048620594
такая вот панорама 😀
custom 52604809649575804067custom 54543530528048620595custom 52581234788836527114custom 54114150750408068851
пермь'25 посикунчики поели, на катере прокатились, посмотрели на город и каму, фото сделали, пермь любим 💋
custom 528541986436049876712custom 54114150750408068857custom 52581234788836527115
ставлю пермскому краю 10/10
custom 52581234788836527119custom 52854198643604987679custom 52604809649575804066
сходили в воскресенье на аттракционы в парк Маяковского🤩 очень страшно, рекомендую!👍
custom 52604809649575804067custom 54114150750408068857custom 52854198643604987676custom 54543530528048620591
альпаки вообще супер милые мягкие и пушистые, можно их погладить даже аккуратно всем советую сходить! и наверное ближе к вечеру, там очень красиво подсвечиваются фонарики, плюс есть оборудованые места для отдыха, так же для посетителей предусмотрено чай/кофе и угощение к ним мы ходили утром, но хорошее настроение осталось на целый день🫶
custom 54114150750408068859custom 52604809649575804068custom 52854198643604987676
любовь за морковь только:(
custom 52604809649575804067custom 54543530528048620595custom 52581234788836527114
сегодня был день милашек!! 📍парк альпак (ул. пески, 60)
custom 52854198643604987678custom 52581234788836527114custom 54543530528048620594custom 52604809649575804062
деревенский вайбик
custom 525812347888365271111custom 54543530528048620596custom 54114150750408068855custom 52604809649575804063
Showing the 9 most recent of 9 posts we hold for @tgquasiiik. 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.
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.
“без названия” (@tgquasiiik), 56 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/tgquasiiik.
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.