Video, posted without a caption
Signed tmeluckyy
![Telegram profile photo for Лакки и А330 [ клан сыр ]](https://cdn.tgregister.com/av/f3/f31f2795ca968f45e786a2e24f432f598179e96e14b40d532ba2c4f065bd1bb2.jpg)
Channel
@tmeluckychannel
On this record: Topic · Growth · Engagement · Posts · Cite this entry
108subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002062641084 |
|---|---|
| Type | Channel |
| Username | @tmeluckychannel |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/tmeluckychannel |
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 17:09 | 108 | -2 |
| 2 Oct 2026, 09:58 | 110 | +4 |
| 16 Sept 2026, 22:22 | 106 | -1 |
| 9 Sept 2026, 22:21 | 107 | +1 |
| 31 Aug 2026, 11:11 | 106 | -2 |
| 16 Aug 2026, 18:23 | 108 | -2 |
| 9 Aug 2026, 07:31 | 110 | no change |
| 7 Aug 2026, 16:03 | 110 | first reading |
20 posts held, back to 4 August 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.
Video, posted without a caption
Signed tmeluckyy
Завтра
Signed tmeluckyy
Стрим отмена сорян
Signed tmeluckyy
В 20:30
Signed tmeluckyy
Буду выживать на сервере HypeMC, я там модер кста
Signed tmeluckyy
Сегодня стрим по майнкрафту
Signed tmeluckyy
https://www.twitch.tv/tmeluckyy GO
Signed tmeluckyy
щас захожу в кску
Signed tmeluckyy
Лакки и Лето pinned «НАБОР СТРОИТЕЛЕЙ ДЛЯ ПОСТРОЙКИ МОЕГО СЕРВЕРА JumboMC. ПИШИТЕ В ЛС @tmeluckyy»
НАБОР СТРОИТЕЛЕЙ ДЛЯ ПОСТРОЙКИ МОЕГО СЕРВЕРА JumboMC. ПИШИТЕ В ЛС @tmeluckyy
Signed tmeluckyy
А пока что
Signed tmeluckyy
Типа поняли ок?
Signed tmeluckyy
Showing the 12 most recent of 20 posts we hold for @tmeluckychannel. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Лакки и А330 [ клан сыр ]” (@tmeluckychannel), 108 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/tmeluckychannel.
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.