Telegram RegisterThe public register of Telegram
Telegram profile photo for Armmez

Channel

Armmez

@armmez

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

175subscribers

-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-1001608798179
TypeChannel
Username@armmez
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live29 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/armmez

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

175178176.57 August 2026 — 176 subscribers15 August 2026 — 175 subscribers23 August 2026 — 176 subscribers16 September 2026 — 177 subscribers29 September 2026 — 178 subscribers9 October 2026 — 178 subscribers9 October 2026 — 176 subscribers16 October 2026 — 177 subscribers23 October 2026 — 176 subscribers29 October 2026 — 175 subscribers7 August 202629 October 2026
10 measurements spanning 83 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 175–178 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 13:59175-1
23 Oct 2026, 05:19176-1
16 Oct 2026, 08:06177+1
9 Oct 2026, 08:36176-2
9 Oct 2026, 03:22178no change
29 Sept 2026, 23:19178+1
16 Sept 2026, 09:36177+1
23 Aug 2026, 12:48176+1
15 Aug 2026, 17:44175-1
7 Aug 2026, 16:57176first reading

Engagement

7 posts held, back to 18 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
54.9%
avg views ÷ 175 subscribers
Avg views / post
96.0
2 posts measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
2
of 7 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 2 October 2026
Posts held7 (18 September 2026 – 2 October 2026)
Views total192
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Oct 2026, 03:22 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.

What this channel posts

Video runtime
20s
Average length
20s

Measured directly from 1 video 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

125 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 23.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52446736728321092922923.2%
custom 54542836676081888912721.6%
custom 54678386917685514922520.0%
custom 53482502064942734192318.4%
custom 54565135974484076331512.0%
custom 543855758472437448264.80%

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 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 125 reactions 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 18 September 2026 to 2 October 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

2 Oct 2026, 17:20 UTC92 views16 reactionsread 9 October 2026
Photo

🤩Делать закос на Викторию ?❤️

custom 54542836676081888918custom 52446736728321092924custom 53482502064942734193custom 54565135974484076331

2 Oct 2026, 12:51 UTC100 views6 reactionsread 9 October 2026
Video message

Video message, posted without a caption

custom 53482502064942734192custom 54565135974484076332custom 52446736728321092921custom 54542836676081888911

1 Oct 2026, 19:02 UTC100 views17 reactionsread 9 October 2026
Photo

Меня уже напрягает , что я ставлю так руку , не только для фото 🌟

custom 52446736728321092929custom 54542836676081888914custom 54565135974484076333custom 54678386917685514921

1 Oct 2026, 07:10 UTC102 views26 reactionsread 9 October 2026
Photo

Куда я попала ..

custom 546783869176855149212custom 54565135974484076336custom 54385575847243744825custom 53482502064942734192custom 52446736728321092921

26 Sept 2026, 16:19 UTC156 views24 reactionsread 9 October 2026
Photo

🍁С фанатами

custom 534825020649427341915custom 54542836676081888915custom 52446736728321092923custom 54385575847243744821

23 Sept 2026, 03:06 UTC185 views24 reactionsread 9 October 2026
Photo

🎀Ну немного вайб осени имеется

custom 524467367283210929211custom 54542836676081888916custom 54678386917685514926custom 54565135974484076331

18 Sept 2026, 15:08 UTC206 views12 reactionsread 9 October 2026
Photo

Последняя неделя ощущается как пост из неподходящих друг к другу моментов

custom 54678386917685514926custom 54542836676081888913custom 54565135974484076332custom 53482502064942734191

Showing the 7 most recent of 7 posts we hold for @armmez. 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Armmez” (@armmez), 175 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/armmez.

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.