Telegram RegisterThe public register of Telegram
Telegram profile photo for Mairon_R

Channel

Mairon_R

@maironRart

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

28subscribers

+1 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-1002394105373
TypeChannel
Username@maironRart
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/maironRart

Growth

272827.59 August 2026 — 27 subscribers11 August 2026 — 27 subscribers17 August 2026 — 28 subscribers9 August 202617 August 2026
3 measurements spanning 8 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 27–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:4728+1
11 Aug 2026, 06:4727no change
9 Aug 2026, 08:3027first reading

Engagement

11 posts held, back to 31 December 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.

ERR · 30 days
89.3%
avg views ÷ 28 subscribers
Avg views / post
25.0
1 post measured
Reaction rate
32.0%
reactions ÷ views · ER floor
Posts in window
1
of 11 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 19 July 2026
Posts held11 (31 December 202519 July 2026)
Views total25
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 06:47 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
1m 22s
Average length
1m 22s

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

113 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 39.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4539.8%
2320.4%
🥰1815.9%
❤‍🔥87.08%
🌚65.31%
🌭21.77%
🍌21.77%
🎉21.77%
💋21.77%
🤝21.77%
🐳10.885%
😎10.885%
🫡10.885%

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

Measured over the 11 most recent posts we hold, published 31 December 2025 to 19 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.

Recent posts

19 Jul 2026, 16:18 UTC25 views8 reactionsread 11 August 2026
Forwarded from @NikaPhantomPhoto

Подарочек на день рождения для ДМа, мини Силбриг💙 #днд_ос

🥰8

17 Jul 2026, 16:30 UTC40 views11 reactionsread 11 August 2026
Photo

Сегодня у меня др и в плане артов пока этот год самый тухлый. Причина тому чреда разных событий, как хороших, так и плохих. Постепенно реанимируюсь и медленно вхожу обратно в ритм. В работе есть несколько полноценок, но некоторые еще не готовы, а некоторые пока нельзя показывать. Так или иначе сейчас ощущаю как катастрофически не хватает времени. Но ничего! Сейчас я чувствую себя намного лучше, надо просто свыкнуться

9🔥2

20 May 2026, 15:26 UTC71 views13 reactionsread 11 August 2026
Photo

Кто его романсит, тот конченный долбаеб (я его романсила и повторю этот подвиг снова) #fanart #wh40k #roguetrader #marazhai

🔥13

11 Mar 2026, 08:44 UTC97 views16 reactionsread 11 August 2026
Photo

Prepare for trouble and make it doble 🫣 #dnd #oc

🔥9❤‍🔥52

28 Feb 2026, 15:32 UTC79 views20 reactionsread 11 August 2026
Photo

Портрет для нового загадочного нпс, который вчера предстал перед игроками 😶‍🌫 #dnd #oc

🌚6🥰4🌭2🍌21🐳1🔥1🤝1

15 Jan 2026, 13:59 UTC89 views2 reactionsread 11 August 2026

Эта вуман реально сделала трейлер к днд арке в которую мы сейчас играем Я в шоках я целую ей руки 😩🙏🙏🙏🙏

1🎉1

15 Jan 2026, 13:59 UTC85 views7 reactionsread 11 August 2026
Forwarded from @icysidneyVideo

Вот он, мой магнум опус, работа, занявшая у меня больше двух месяцев, мой грандиозный подарок самым лучшим на свете игрокам в днд ✨ Мона, Меттью, Айан и Алард, и большое количество моих старых и новых персонажей. Надеюсь, это не последняя моя подобная работа #DnD

🔥6🎉1

15 Jan 2026, 04:22 UTC59 views3 reactionsread 11 August 2026

ПОСМОТРИТЕ НА ЛУК ЭТОГО ПАЦАНЧИКА НУ КАКОЙ ОН МОДНЯВЫЙ ЗУМЕР🙏

🥰21

15 Jan 2026, 04:22 UTC73 views6 reactionsread 11 August 2026
Forwarded from @NikaPhantomPhoto

🖇️ОФИС готов! Ещё раз поздравляю моих чудесных ДМов и игроков! Итак, кто же у нас чем занят. Лерой - главный по связям с общественностью/SMM, получает самую большую ЗП Айан - курьер, доставляет документы, ценные бумаги, делает 10 дел одновременно Мона - бухгалтер/товаровед, пытается поддерживать порядок Алард - охранник/кладовщик, большую часть времени в наушниках Керри - разработчик, игнорирует дресс-код Мэттью - юр

🔥5🥰1

10 Jan 2026, 13:02 UTC881 views12 reactionsread 11 August 2026
Photo

Новогодние мини-презентики для @icysidney @NikaPhantom @mrg_dm_art @lixastuff 🌲

🔥9❤‍🔥3

31 Dec 2025, 09:01 UTC88 views15 reactionsread 11 August 2026
Photo

Таки сделала итоги года. В этом году мне невероятно "повезло" и прямо перед нг я умудрилась заболеть, и несколько дней валялась с температурой, благо хоть сегодня её нет, но состояние все еще оставляет желать лучшего, встречать новый год в таком самочувствии просто во 👍 Но не будем о грустном, в плане артов этот год, по ощущениям, оказался менее продуктивным чем предыдущий, много недоделок которые ждут своего часа, к

9🥰3💋2🤝1

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

Citation-graph rank

Citation-graph rank — 953,812 of 1,481,502entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Mentions

Named by 3 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Mairon_R” (@maironRart), 28 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/maironRart.

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.