3 measurements taken within a single day, 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 860–861 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 12:34
860
-1
8 Aug 2026, 19:00
861
no change
8 Aug 2026, 18:48
861
first reading
Engagement
7 posts held, back to 10 April 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
35.2%
avg views ÷ 860 subscribers
Avg views / post
303
2 posts measured
Reaction rate
6.61%
reactions ÷ views · ER floor
Posts in window
3
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
Window
Rolling 30 days · latest post in window 29 July 2026
Posts held
7 (10 April 2026 – 29 July 2026)
Views total
605
Reactions total
40
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 19:00 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.
Reaction mix
77 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 80.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
62
80.5%
🔥
13
16.9%
👎
2
2.60%
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 6 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 77reactions 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 10 April 2026 to 29 July 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.
Немножко из мира российского ритэйла
На днях мой давний хороший друг Вячеслав Кухта сообщил об удивительной находке с Яндекс.Карт — оказывается, в Чебоксарах ещё можно посетить Евросеть, но с условием)
Билайн не стал менять фасад магазина и оставил как есть, скорее всего из-за отсутствия бюджета на ремонт магазина, но сам факт очень удивителен. До последнего думал что просто забытая точка с Яшки, пока не увидел нов…
🤝🤝 Сегодня про Nokia Data MikroMikko
Да-да, Nokia, известная большинству из нас в основном только как производитель телефонов и смартфонов, производила компьютеры!
Естественно, это было подразделение финской компании - Nokia Data
Происходило это в 80-х и это объективно было лучшим временем для развития компьютеров. В то время уже начали отходить от того прежнего стереотипа что компьютеры воспринимались прежде всег…
Что говорить про несчастный обзор на Galaxy S5 и 7-ой выпуск Интервью, то они ещё в работе и стараюсь к ним как можно быстрее вернуться, чтобы их уже завершить ей богу, так что следите за новостями канала. Постов новых новостных постараюсь тоже подвести, просто пытаюсь выбраться из апатии, давно пора
#OMC
Я как обычно пропустил все дедлайны и планы, за что дико извиняюсь, самому очень обидно что сильно подвёл вас своим отсутствием мотивации и сил заниматься ОМС, но при этом сворачивать проект пока не горю желанием, и что же я предложу?
Было бы круто собрать команду, что готова уделять время проекту и возможно даже порассказывать про свои трубки из коллекции или из жизни. Если вы увлекаетесь старыми трубками, ес…
#OMC #Motorola
📟 До релиза Motorola AURA, в 2008 году гуляли в интернете фотографии прототипы некого V70 Retro, подозрительно похожего на Ауру. Фотографии модели всплывали на сайте FCC и известно лишь то, что модель будет наследником V70 (вышедшей в 2002 году), характеристики очевидно будут мощнее, а также обживется 5-мегапиксельной камерой.
Сама Motorola AURA вышла в релиз в конце 2008 года, являющийся люксовой тр…
❤10
Showing the 7 most recent of 7 posts we hold for @omc_mobile. 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
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.
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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“Old Mobile Community” (@omc_mobile), 860 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/omc_mobile.
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.
