๐๐ข๐ ๐ ๐ง๐ข ๐ข๐จ๐ฅ ๐๐๐๐ข๐ฆ ๐
customย 617897981306418445715customย 61523121764397259205customย 61817254825773019904customย 62919324707869206604customย 62939386457159165283

Channel
@SeansOfc
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry
792subscribers
-6 since we began measuring on 13 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002465458700 |
|---|---|
| Type | Channel |
| Username | @SeansOfc |
| Created | Between 1 September 2024 and 31 March 2025 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/SeansOfc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 18:57 | 792 | +10 |
| 29 Aug 2026, 18:57 | 782 | -11 |
| 22 Aug 2026, 06:17 | 793 | -7 |
| 14 Aug 2026, 09:26 | 800 | +2 |
| 13 Aug 2026, 18:15 | 798 | no change |
| 13 Aug 2026, 18:04 | 798 | first reading |
16 posts held, back to 26 May 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ we hold 16 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 videos 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.
418 reactions across 8 posts, in 11 distinct kinds. The most used accounts for 42.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ฅ | 177 | 42.3% | |
| โคโ๐ฅ | 128 | 30.6% | |
| customย 6178979813064184457 | 35 | 8.37% | |
| ๐ | 35 | 8.37% | |
| customย 6291932470786920660 | 9 | 2.15% | |
| customย 6293938645715916528 | 9 | 2.15% | |
| customย 6152312176439725920 | 8 | 1.91% | |
| customย 6181725482577301990 | 6 | 1.44% | |
| customย 6145433408358061819 | 5 | 1.20% | |
| customย 6289511440671838917 | 4 | 0.957% | |
| โก | 2 | 0.478% |
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 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 8 of the 16 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 418 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 16 most recent posts we hold, published 26 May 2026 to 9 August 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.
๐๐ข๐ ๐ ๐ง๐ข ๐ข๐จ๐ฅ ๐๐๐๐ข๐ฆ ๐
customย 617897981306418445715customย 61523121764397259205customย 61817254825773019904customย 62919324707869206604customย 62939386457159165283
Sticker, posted without a caption
move t.me/caughtbysean
customย 61789798130641844578customย 62919324707869206605customย 62895114406718389174customย 62939386457159165284
Sticker, posted without a caption
๐๐๐ก๐๐๐ก ๐ฆ๐ข๐๐๐ฃ ๐๐ ๐๐ข ๐๐จ๐๐๐ก ๐ฆ๐๐๐ก๐
๐ฅ108๐10โคโ๐ฅ7customย 61789798130641844576โก2customย 61454334083580618192customย 61523121764397259201
Sticker, posted without a caption
see u @OfficialForza๐๐ป
๐ฅ48๐8โคโ๐ฅ7customย 61789798130641844572customย 61454334083580618191customย 61523121764397259201
Sticker, posted without a caption
๐ฆ๐๐๐ฃ ๐๐๐ก๐๐จ๐ฅ ๐๐๐ก๐๐จ๐ฅ๐๐ก๐
โคโ๐ฅ17๐ฅ14๐9customย 61454334083580618191customย 61789798130641844571customย 61817254825773019901customย 62939386457159165281
Sticker, posted without a caption
๐๐๐๐๐๐๐๐๐ - ๐๐๐ฌ๐ญ๐๐๐ง๐๐. pinned ยซ๐๐ผ๐บ๐ฒ ๐๐ป๐ฑ ๐๐ถ๐๐ฒ ๐ฆ๐๐๐ก๐ข๐๐๐๐ฉ๐๐ข๐ก - ๐ฃ๐๐ฏ๐น๐ถ๐ฐ. ๐ฆ๐๐๐ก๐ฆ๐ง๐๐ง๐๐ - ๐ฃ๐ฟ๐ถ๐๐ฎ๐๐ฒ.ยป
๐๐ผ๐บ๐ฒ ๐๐ป๐ฑ ๐๐ถ๐๐ฒ ๐ฆ๐๐๐ก๐ข๐๐๐๐ฉ๐๐ข๐ก - ๐ฃ๐๐ฏ๐น๐ถ๐ฐ. ๐ฆ๐๐๐ก๐ฆ๐ง๐๐ง๐๐ - ๐ฃ๐ฟ๐ถ๐๐ฎ๐๐ฒ.
๐8โคโ๐ฅ7๐ฅ7customย 61454334083580618191customย 61789798130641844571customย 61817254825773019901
Showing the 12 most recent of 16 posts we hold for @SeansOfc. 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.
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.
Named by 1 registered channel โ 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.
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.
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 7 September 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐๐๐๐๐ - ๐๐๐ฌ๐ญ๐๐๐ง๐๐.โ (@SeansOfc), 792 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/SeansOfc.
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.