Telegram RegisterThe public register of Telegram
Telegram profile photo for Limetta not me🍚

Channel

Limetta not me🍚

@limettanotme

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

407subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002225691339
TypeChannel
Username@limettanotme
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/limettanotme

Topic

Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

400409404.57 August 2026 — 400 subscribers8 August 2026 — 400 subscribers14 August 2026 — 401 subscribers21 August 2026 — 405 subscribers27 August 2026 — 408 subscribers5 September 2026 — 409 subscribers8 October 2026 — 407 subscribers4077 August 20268 October 2026
7 measurements spanning 62 days, net +7. 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 399–410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 06:41407-2
5 Sept 2026, 02:59409+1
27 Aug 2026, 08:43408+3
21 Aug 2026, 03:15405+4
14 Aug 2026, 08:24401+1
8 Aug 2026, 05:48400no change
7 Aug 2026, 16:55400first reading

Engagement

5 posts held, back to 12 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 5 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
16s
Average length
16s

Measured directly from 1 video 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.

Reaction mix

250 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 37.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53796694470426913449337.2%
❤‍🔥5120.4%
🍓4216.8%
custom 52242702975484806723212.8%
custom 52244087071645618302510.0%
custom 522439023880519151931.20%
custom 537748445115032505431.20%
💋10.4%

Custom emoji. 5 of the rows above are 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 5 of the 5 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 250 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 12 July 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.

Recent posts

6 Aug 2026, 10:09 UTC258 views48 reactionsread 8 August 2026
Photo

Переплыли Лену, чтобы посмотреть на дюны Тукуланы поразили своей красотой: с их вершины открывается вид на просторы тайги Взяли с собой доску для сэндсёрфинга 🌊🏄

🍓22custom 537966944704269134413custom 522427029754848067211❤‍🔥1custom 52243902388051915191

31 Jul 2026, 15:33 UTC465 views34 reactionsread 8 August 2026
Photo

Особенности Махтала: 1. Бумажки, где мы должны были написать наши желания. Во время чайной церемонии они сжигались на удачу 2. Салат индигирка 3. Десерт мартышка

❤‍🔥16🍓9custom 53796694470426913447custom 52243902388051915192

31 Jul 2026, 15:30 UTC448 views36 reactionsread 8 August 2026
Photo

Саха Сирэ [Якутия] В самом начале нашей поездке нам не повезло с погодой — Якутск предстал совсем серым, туманным Но город оказался очень интересным: все дома стоят на сваях из-за «вечной мерзлоты» Начали гулять по городу и все исследовать нашей компанией, в местный магазинчиках нашли быырпах - традиционный якутский напиток по типу айрана Таксист, который был здесь в командировке, посоветовал съездить в ресторан …

custom 537966944704269134418🍓9❤‍🔥8custom 52244087071645618301

28 Jul 2026, 12:34 UTC589 views81 reactionsread 8 August 2026
Photo

Собираюсь на второй бакалавриат Жить надо так, что даже ты не знаешь свой следующий шаг — отдала документы в предпоследний день Подала олимпиаду в другой вуз, но по баллам (306) все равно прохожу на бюджет во ВШЭ :: И скоро опубликую все с путешествия по Дальнему Востоку🤍🤍

custom 537966944704269134442custom 522427029754848067221custom 522440870716456183016💋1custom 53774844511503250541

12 Jul 2026, 20:31 UTC979 views51 reactionsread 8 August 2026

Отправились в путешествие на Дальний Восток!

❤‍🔥26custom 537966944704269134413custom 52244087071645618308🍓2custom 53774844511503250542

Showing the 5 most recent of 5 posts we hold for @limettanotme. 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.

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

“Limetta not me🍚” (@limettanotme), 407 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/limettanotme.

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.