Personal blog — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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 the other topics.
Growth
36 measurements spanning 62 days, net +2,099. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)
Subscribers
Change
7 Nov 2026, 10:18
48,364
+152
6 Nov 2026, 10:16
48,212
+111
5 Nov 2026, 09:39
48,101
+17
4 Nov 2026, 12:26
48,084
+38
3 Nov 2026, 09:16
48,046
+45
2 Nov 2026, 12:27
48,001
+49
1 Nov 2026, 09:06
47,952
+51
31 Oct 2026, 08:36
47,901
+13
30 Oct 2026, 07:19
47,888
+85
29 Oct 2026, 04:58
47,803
+130
28 Oct 2026, 01:50
47,673
+27
26 Oct 2026, 22:31
47,646
+23
25 Oct 2026, 21:11
47,623
+63
25 Oct 2026, 00:09
47,560
+15
23 Oct 2026, 22:27
47,545
+24
22 Oct 2026, 18:56
47,521
+13
21 Oct 2026, 16:19
47,508
+10
20 Oct 2026, 14:40
47,498
+39
19 Oct 2026, 15:39
47,459
+30
18 Oct 2026, 15:48
47,429
first reading
Engagement
101 posts held, back to 4 September 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 36 pages 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 101 posts for this entry, the most recent from 24 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
2m 52s
Average length
34s
Measured directly from 5 videos 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
21,999 reactions across 98 posts, in 17 distinct kinds. The most used accounts for 72.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤣
15,969
72.6%
❤
4,261
19.4%
😭
912
4.15%
😢
301
1.37%
🌚
163
0.741%
🍓
145
0.659%
🔥
58
0.264%
🎉
43
0.195%
🥰
35
0.159%
😁
27
0.123%
❤🔥
23
0.105%
👏
22
0.1%
👀
19
0.086%
💯
10
0.045%
🐳
5
0.023%
🕊
5
0.023%
🙏
1
0.005%
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 98 of the 101 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 21,999 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 101 most recent posts we hold, published 4 September 2026 to 24 September 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.
ချစ်စရာအကောင်းဆုံးလေးတွေအတွက်ထုတ်ပေးတဲ့ Event ကပုံတဲ့ ပီတာနဲ့သူ့ဒယ်ဒီချယ်စီတို့ဆုံတာလေးလဲမြင်ချင်မိပြီရှင်
Kiss Me If You Can 🔻
https://t.me/KissMeIfYouCan_PannMyat
Desire Me If You Can 🔻
https://t.me/IfYouCan_PannMyat
သားရွှေအိုးထမ်းလာတာ မမြင်ရလည်းနေ
သားတို့ချင်းချင်း ချစ်ကြိုက်တာပဲမြင်ချင်တော့တယ် ဟင့် ՞߹ - ߹՞
Yang II Woo and I -33 done ✅ (Ongoing မှီ)
https://t.me/yangillwooandi_PannMyat
Showing the 12 most recent of 101 posts we hold for @PannMyatTranslation. 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.
Posts edited after publishing
@PannMyatTranslation edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
16 September 2026
Most recent edit
16 September 2026
Posts recorded as deleted after publishing
We recorded 1 post on @PannMyatTranslation as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
7 September 2026
Most recent seen missing
7 September 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
0
Mentions
Named by 22 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.
Named by
Channels on the register whose posts name this channel's handle.
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 7 November 2026 — this
entry's latest reading, not the date you are reading this.
“PannMyat Translation 🌸” (@PannMyatTranslation), 48,364 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/PannMyatTranslation.
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.
