Telegram RegisterThe public register of Telegram
Telegram profile photo for Montana Pubgm

Channel

Montana Pubgm

@Twpwildpower

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

39subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002078588124
TypeChannel
Username@Twpwildpower
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/Twpwildpower

Growth

394039.57 August 2026 — 40 subscribers10 August 2026 — 40 subscribers28 August 2026 — 39 subscribers7 August 202628 August 2026
3 measurements spanning 21 days, net -1. 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 39–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 21:1439-1
10 Aug 2026, 19:1640no change
7 Aug 2026, 16:2740first reading

Engagement

7 posts held, back to 14 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 7 posts for this entry, the most recent from 16 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

40 reactions across 7 posts, in 12 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1230.0%
custom 5406813825036993783410.0%
🍾410.0%
🎃410.0%
🎄410.0%
😎37.50%
custom 540663357814448350225.00%
custom 622861413017400279625.00%
💋25.00%
custom 538427717815213908912.50%
custom 541138735102691282712.50%
custom 545400979472360124812.50%

Custom emoji. 6 of the rows above are 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 areTelegram’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 7 of the 7 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 40reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 14 September 2025 to 16 November 2025, 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

16 Nov 2025, 20:45 UTC194 views5 reactionsread 10 August 2026

game : Cs 2 \ Cs 1.6 https://youtube.com/live/vLHiap-6hJM?si=QilTjq86FOjK-ipB

2🎃2😎1

23 Oct 2025, 13:44 UTC78 views5 reactionsread 10 August 2026
Photo

✏️Royal Pass A16✏️ Как вам? Ждём реакций❤️ 🥰 - офигенно,ждём 🎄 - всё равно 🍾 - копим юси 🎃 - мне не нравится

🎄3🎃1😎1

21 Oct 2025, 17:53 UTC75 views6 reactionsread 10 August 2026
Photo

✏️Награды C9S27 сезона✏️ Как вам? Ждём реакций❤️ 🥰 - круто,ждём 🎄 - для коллекции пойдет 🍾 - мне не нравится 🎃 - всё равно

🍾3💋2🎃1

19 Sept 2025, 16:06 UTC190 views7 reactionsread 10 August 2026
Photo

❤️‍🩹

3custom 62286141301740027962😎1custom 54540097947236012481

17 Sept 2025, 16:41 UTC220 views7 reactionsread 10 August 2026
Photo

✏️В обновлении 4.1

2custom 54066335781444835022custom 54068138250369937832custom 53842771781521390891

14 Sept 2025, 22:04 UTC62 views5 reactionsread 10 August 2026
Photo

Cs 🤓

2custom 54068138250369937832custom 54113873510269128271

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

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

“Montana Pubgm” (@Twpwildpower), 39 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/Twpwildpower.

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.