Telegram RegisterThe public register of Telegram
Telegram profile photo for t.leeknowsaurus .

Channel

t.leeknowsaurus .

@mi3neko

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,918subscribers

+49 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002080258966
TypeChannel
Username@mi3neko
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live5 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/mi3neko

Growth

1,8691,9421,905.511 August 2026 — 1,869 subscribers11 August 2026 — 1,870 subscribers14 August 2026 — 1,902 subscribers17 August 2026 — 1,932 subscribers20 August 2026 — 1,916 subscribers23 August 2026 — 1,906 subscribers26 August 2026 — 1,897 subscribers29 August 2026 — 1,942 subscribers1 September 2026 — 1,930 subscribers5 September 2026 — 1,918 subscribers1,91811 August 20265 September 2026
10 measurements spanning 25 days, net +49. 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 1,858–1,953 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 00:571,918-12
1 Sept 2026, 14:041,930-12
29 Aug 2026, 21:241,942+45
26 Aug 2026, 16:341,897-9
23 Aug 2026, 22:461,906-10
20 Aug 2026, 16:261,916-16
17 Aug 2026, 16:161,932+30
14 Aug 2026, 05:351,902+32
11 Aug 2026, 08:181,870+1
11 Aug 2026, 03:451,869first reading

Engagement

20 posts held, back to 23 July 2026the 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.

ERR · 30 days
2.88%
avg views ÷ 1,918 subscribers
Avg views / post
55.3
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held20 (23 July 20269 August 2026)
Views total332
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 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.

Recent posts

9 Aug 2026, 19:58 UTC58 viewsread 11 August 2026
Forwarded from @gnabnac

‌ ‌ ‌ ㅤ🎐 : 방찬 ’s zone. ㅤ太陽 in stay's birthday live .

9 Aug 2026, 19:58 UTC58 viewsread 11 August 2026
Forwarded from @gnabnacSticker

Sticker, posted without a caption

9 Aug 2026, 19:58 UTC52 viewsread 11 August 2026
Forwarded from @binnung

‌ ‌ ‌ ㅤ🔮 : 창빈 ’s zone. ㅤのあ in stay's birthday live .

9 Aug 2026, 19:58 UTC53 viewsread 11 August 2026
Forwarded from @binnungSticker

Sticker, posted without a caption

9 Aug 2026, 19:58 UTC57 viewsread 11 August 2026
Forwarded from @s1netteSticker

Sticker, posted without a caption

9 Aug 2026, 19:58 UTC54 viewsread 11 August 2026
Forwarded from @s1nette

‌ ‌ ‌ ㅤ🍭 : 승민 ’s zone. ㅤみず in stay's birthday party .

30 Jul 2026, 10:51 UTC275 viewsread 11 August 2026
Forwarded from @lixttunSticker

Sticker, posted without a caption

30 Jul 2026, 10:51 UTC268 viewsread 11 August 2026
Forwarded from @lixttun

‌ ‌ ‌ ㅤ🥟 : 필릭스 ’s zone . ㅤはく in racha log ep 22 .

30 Jul 2026, 10:51 UTC275 viewsread 11 August 2026
Forwarded from @lixttunSticker

Sticker, posted without a caption

30 Jul 2026, 10:51 UTC259 viewsread 11 August 2026
Forwarded from @lixttun

‌ ‌ ‌ ㅤ🍙 : 필릭스 ’s zone . ㅤはく in skz code ep 91 .

30 Jul 2026, 10:51 UTC240 viewsread 11 August 2026
Forwarded from @hyusaceSticker

Sticker, posted without a caption

30 Jul 2026, 10:51 UTC214 viewsread 11 August 2026
Forwarded from @hyusace

‌ ‌ ‌ ㅤ💿 : 현진 ’s zone . ㅤつき in racha log ep 25 .

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

Named by 2 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“t.leeknowsaurus .” (@mi3neko), 1,918 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/mi3neko.

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.