Telegram RegisterThe public register of Telegram
Telegram profile photo for ㅤмяу

Channel

ㅤмяу

@irohainfo

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

1subscribers

-147 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002675098664
TypeChannel
Username@irohainfo
Created30 May 2025 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live5 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/irohainfo

Topic

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 5 October 2026 and assigned it the closest of 31 fixed categories, at 55% 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

1161819 August 2026 — 148 subscribers10 August 2026 — 148 subscribers17 August 2026 — 146 subscribers24 August 2026 — 161 subscribers5 October 2026 — 1 subscribers9 August 20265 October 2026
5 measurements spanning 57 days, net -147. 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
Measured (UTC)SubscribersChange
5 Oct 2026, 10:381-160
24 Aug 2026, 17:04161+15
17 Aug 2026, 19:14146-2
10 Aug 2026, 08:43148no change
9 Aug 2026, 16:46148first reading

Engagement

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

Reaction mix

19 reactions across 1 post, in 8 distinct kinds. The most used accounts for 31.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5280672770152237682631.6%
custom 5283031441637148958421.1%
custom 5282771355597573467210.5%
custom 5283003653198744187210.5%
custom 5283030196096636042210.5%
custom 528296427693857254115.26%
custom 528313469265094685815.26%
custom 528327144440965266015.26%

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 1 of the 3 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 30 May 2025 to 9 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

9 Aug 2026, 09:46 UTC16 viewsread 9 August 2026
Forwarded from @muIpaPhoto

ㅤㅤㅤ‌թᤢ⃪𖹭ິ⃪ۣзыгթᤢ⃪ыш н𝝰ꥋׂ 𝟐𝟓𝐎 зϐ⃪езд ϐ⃪ ч𝗲сть ო⵿ۣ⃜ؖ᷼𑄜⃪ۣ𝗲го д𝗲нь թᤢ⃪𑄜⃪ۣжд𝗲нья fr𑄜⃪ۣm @muIpa ㅤЧт𑄜⃪ۣ нужн𑄜⃪ۣ для уч𝝰ꥋׂстия? 𝓸𝓸𝟏 п𑄜⃪ۣдпи⃪⃜ска на инф𖹭ິ⃪ۣ б𝗲з д𝝰ꥋׂльн𝗲йшей 𑄜⃪ۣтпи⃪⃜ски 𝓸𝓸𝟐 թᤢ⃪т в 𝝰ꥋׂкт𝘂⃪𝅼۫вный кн 𝟐𝟓+ н𝗲 ст𝘂⃪𝅼۫к𝗲р𖹭ິ⃪ۣм 𝓸𝓸𝟑 сс н𝝰ꥋׂ թᤢ⃪т и юз м𑄜⃪ۣно шр𝘂⃪𝅼۫фт𑄜⃪ۣм 𝓸𝓸𝟒 н𝝰ꥋׂпи⃪⃜с𝝰ꥋׂть св𑄜⃪ۣй п𑄜⃪ۣрядк𑄜⃪ۣвый н𑄜⃪ۣм𝗲р 𝟏 м𝗲ст𑄜⃪ۣ 𝟏𝟐𝟓 ☆ 𝟐 м𝗲ст𑄜⃪ۣ 𝟕𝟓 ☆ 3 м𝗲ст𑄜⃪ۣ 𝟓𝐎 ☆ Пр𝘂⃪𝅼۫ не р𝝰ꥋׂб𑄜⃪ۣчей сс я 𝝰ꥋׂннули⃪⃜роваю вас. Ук𝝰ꥋׂзы

Signed ׅㅤ ׂׂ𝆋 ㅤ꒰ᩫᰰ᪾𝅼֗ ❘❙⋮ ꥋ 𝘂ְ࣪҆𝗽ᦢᜒ⃪ֵ݄⃛͢𝘅𝗮 ۟ の۪࣫𑩒ꨲ࣪᪾㫈ུ ࣪ ֢

30 Jun 2026, 12:28 UTC236 views19 reactionsread 9 August 2026
Photo

˖ㅤִ𝆹۪ ࣪᭸‌꛱ 𓈒꒰ᩫᰰ᪾𝅼֗ ❘❙⋮ ꥋ𓏴ۣۛۙ🌟ྀིꢾۣ࣫ܳ۟᷼‌𐇽፝֟ꨲೢࣶࣥ💕𝗽ᦢᜒ݄‌ֵ𝘅𝗮 I ‌ ְׁۜ🌟. .݄᎒ 𓏻ّ ˛‌ᩙገ⃪ۭ݊۠܏᎔࡙ٟࣼؖ‌ .🌟🌟🌟 ⒊᮫ㅤ۰۫᱒۪⃛⃕֩ۧۨ❨ۜ‌⃪𝗺ֵ۫ꨵ𐐼ֱܸ݀۬𝕕ᦢᜒ݄‌ֵ𝗸𐐼⃪ ៸៸𝐢꯭َ𝗿𝓵⃪ ֵ۫✿݄𖽾ִֵْ֒۫۫ᩙ꣒𝘀⃪॒۟𝗽𝟐ᵗ᷒ᰰ 🌟❩⃪ؖ ׅ۫ ○ۖ݊𓏴‌۫ۙᩙ 𝕕𝗺ֵ۫ꨵ ֿ𐇽⃔𓏶ܱܳۜ‌ 𝕕𝒏ׅ𝐢⃪࣯ׅׅׅ 🌟࠾ྀི𐇽𝆋ׅۛ֩ᰰ᪶ۢ‌⃘ۖ𐨁 𐇽

custom 52806727701522376826custom 52830314416371489584custom 52827713555975734672custom 52830036531987441872custom 52830301960966360422custom 52829642769385725411custom 52831346926509468581custom 52832714444096526601

Signed ᷼ ֿ᳝̤ؗ̈︵ ֿ̤ؗᦷᩧ᳕𑪔ٓ υ݁թ⃪⃪𑄹⃪᪲᷼᥊𐐼ׄ᷼ 👛︵ֿ᳝̤ؗ̈ ᷼᷼ ֿ᳝̤ؗ̈︵

Showing the 3 most recent of 3 posts we hold for @irohainfo. 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 1 registered channel — 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.

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

“ㅤмяу” (@irohainfo), 1 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/irohainfo.

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.