Telegram RegisterThe public register of Telegram

Channel

✧.* runimon🪻

@runimonart

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

218subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002631302370
TypeChannel
Username@runimonart
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/runimonart

Growth

2188 Aug 2026, 15:31 — 218 subscribers8 Aug 2026, 16:00 — 218 subscribers8 Aug 2026, 15:318 Aug 2026, 16:00
2 measurements taken within a single day. 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 217–219 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 16:00218no change
8 Aug 2026, 15:31218first reading

Engagement

10 posts held, back to 16 April 2026the 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 10 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
24s
Average length
24s

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

200 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 41.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘8341.5%
custom 53350145174473533184120.5%
custom 52376996466707975173015.0%
custom 5235437538935600356178.50%
custom 5443008218815039468105.00%
custom 525168049106874274584.00%
custom 531244226098864113984.00%
💩21.00%
custom 547444298996517295010.5%

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

Measured over the 10 most recent posts we hold, published 16 April 2026 to 6 May 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

6 May 2026, 20:59 UTC264 views21 reactionsread 8 August 2026
Forwarded from @obeymrnobodyVideo

вот если кто-то захочет репостнуть мои работки в честь др 🥺

💘10custom 52516804910687427456custom 53350145174473533184custom 52354375389356003561

2 May 2026, 17:16 UTC294 views18 reactionsread 8 August 2026
Forwarded from @obeymrnobodyPhoto

🧁

💘9custom 52376996466707975175custom 53350145174473533183custom 53124422609886411391

2 May 2026, 17:16 UTC285 views8 reactionsread 8 August 2026

мой сын😇 наконец-то с моделькой!!

custom 53124422609886411395custom 53350145174473533183

1 May 2026, 20:43 UTC282 views21 reactionsread 8 August 2026
Forwarded from @DeivyiPhoto

Ма-ма, мамины ру-у-у-ки..Нежно погладят, станет светлей Мама и дитятко с репо

💘10custom 52376996466707975176custom 53350145174473533185

28 Apr 2026, 20:32 UTC284 views23 reactionsread 8 August 2026
Photo

у приёмыша Коё было недавно день рождение🤩 как жаль, что он ещё дожил как то до своего возраста 🤩🤩 🤩🤩#спойлер #ос #Коё

💘11custom 53350145174473533187custom 52376996466707975173custom 52516804910687427451custom 54744429899651729501

24 Apr 2026, 18:36 UTC282 views27 reactionsread 8 August 2026
Photo

руни в нашумевшей Tomodachi 😨😨 в первый раз делала, потом переделаю когда норм научусь #щп

💘14custom 52376996466707975176custom 53350145174473533185💩2

23 Apr 2026, 16:55 UTC295 views15 reactionsread 8 August 2026
Forwarded from @skkrrripti1Photo

Трейде https://t.me/runimonart ❤️ легенде почет и уважение #трейд

💘7custom 53350145174473533184custom 52354375389356003563custom 52376996466707975171

23 Apr 2026, 16:51 UTC291 views22 reactionsread 8 August 2026
Photo

моя часть на трейд с @skkrrripti1 обычно не беру трейды, но чето настроение такое было😍 🧚‍♀️🧚‍♀️ 🧚‍♀️🧚‍♀️ 🧚‍♀️🧚‍♀️#арт #трейд

custom 523543753893560035610custom 52376996466707975175custom 53350145174473533185💘2

21 Apr 2026, 21:04 UTC195 views23 reactionsread 8 August 2026
Photo

пиздец меня телефон рейджбейтит

💘13custom 53350145174473533184custom 52354375389356003563custom 52376996466707975172custom 52516804910687427451

16 Apr 2026, 21:39 UTC387 views22 reactionsread 8 August 2026
Photo

для моей активной заечки-зажигалочки @Nar1chka🐾 постепенно привожу себя в норму!! #гифт

custom 544300821881503946810💘7custom 52376996466707975172custom 53124422609886411392custom 53350145174473533181

Showing the 10 most recent of 10 posts we hold for @runimonart. 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 — 870,115 of 1,176,251entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 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.

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.

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

“✧.* runimon🪻” (@runimonart), 218 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/runimonart.

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.