Channel
@MontgoIfier
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
6,317subscribers
-70 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001794836301 |
|---|---|
| Type | Channel |
| Username | @MontgoIfier |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/MontgoIfier |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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 |
|---|---|---|
| 15 Sept 2026, 07:38 | 6,317 | +191 |
| 11 Sept 2026, 10:20 | 6,126 | -23 |
| 6 Sept 2026, 08:57 | 6,149 | +20 |
| 1 Sept 2026, 14:54 | 6,129 | -35 |
| 29 Aug 2026, 10:05 | 6,164 | -9 |
| 26 Aug 2026, 03:24 | 6,173 | -35 |
| 23 Aug 2026, 12:26 | 6,208 | -28 |
| 19 Aug 2026, 21:54 | 6,236 | -48 |
| 16 Aug 2026, 20:43 | 6,284 | -39 |
| 13 Aug 2026, 00:25 | 6,323 | -18 |
| 9 Aug 2026, 15:15 | 6,341 | -37 |
| 7 Aug 2026, 00:26 | 6,378 | -9 |
| 6 Aug 2026, 09:32 | 6,387 | first reading |
18 posts held, back to 7 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 9 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 18 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
45 reactions across 7 posts, in 11 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 40.0% | |
| 🔥 | 5 | 11.1% | |
| ⚡ | 4 | 8.89% | |
| 🐳 | 4 | 8.89% | |
| 🦄 | 4 | 8.89% | |
| 🏆 | 3 | 6.67% | |
| ❤🔥 | 2 | 4.44% | |
| 🍓 | 2 | 4.44% | |
| 🆒 | 1 | 2.22% | |
| 🍾 | 1 | 2.22% | |
| 👀 | 1 | 2.22% |
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 7 of the 18 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 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 7 July 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MontgoIfier. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 18 most recent posts we hold for this entry, published 7 July 2026 to 11 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
ㅤㅤ ㅤㅤ♠︎ 𝗧𝗛𝗘 𝗗𝗘𝗖𝗞 𝗛𝗔𝗦 𝗗𝗘𝗔𝗟𝗧 𝗔 𝗖𝗟𝗨𝗘 ♠︎ ㅤㅤㅤㅤㅤㅤㅤㅤㅤ𝕵 / 26 / 13·08 ㅤㅤㅤㅤㅤ ㅤㅤ SIGNAL ACQUIRED.ㅤㅤ ㅤㅤㅤㅤㅤ ㅤ #𝐍𝐚𝐋𝐨𝐯𝐞𝐥𝐲𝐉𝐚𝐞𝐦𝐢𝐧𝐃𝐚𝐲 ㅤThe first card has been drawn, yet the hand ㅤremains unfinished. Follow the trace, read ㅤbetween the signs, and perhaps the missing ㅤname will reveal itself. ♦︎🃏 ㅤㅤ
Ethienss! Tonight, I, Luthien’s Wonyoung, officially entering my ultimate hangout era, and I’ve assembled the absolute dream lineup for maximum chaos: Thimblea's Ian, Montgolfier's Yuha, Liu's Martin, Edurne's Ohyul and Bosche's Ohyul! 👀 Honestly, we’ve all been drowning in our own lives, but tonight? We’re pressing pause on adulting! The second we all met up, it was instant overload, Thimblea's Ian and Montgolfier'…
⚡1❤1🏆1🐳1
Late night adventures hit completely different when you're in good company: a cozy stroll alongside Liu’s Martin & Montgolfier’s Yuha, quick outfit checks under the streetlights and endless quiet stops along dark alleys with absolutely zero rush to call it a night.
❤5🍾1🆒1
Mari ready kan
blm pernah kbtulan a
Pernah ga ready
Video, posted without a caption
ntuls
Sticker, posted without a caption
Posted without readable text
🐳3🦄3⚡2🔥2❤1
Sticker, posted without a caption
It was a long night for me, Ignarev's Riwoo, and Norvein's Woonhak as we wandered outside. After grabbing some coffee, I thought a stroll would be nice, but Norvein's Woonhak was acting so... silly? Just as I tried to take a photo of him, my coffee slipped and spilled everywhere... 😭 Amid the chaos, I spotted Nethers' Myungjae across the road, looking dazed after being chased by a dog. He collided with Etherhails' R…
Showing the 12 most recent of 18 posts we hold for @MontgoIfier. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 101 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Montgolfier: Haven of Petal Artisans.” (@MontgoIfier), 6,317 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/MontgoIfier.
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.