Channel
@seultown
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
738subscribers
-10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001985140762 |
|---|---|
| Type | Channel |
| Username | @seultown |
| Created | 15 September 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/seultown |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 13:17 | 738 | -7 |
| 30 Aug 2026, 12:54 | 745 | +1 |
| 23 Aug 2026, 06:02 | 744 | -4 |
| 7 Aug 2026, 17:22 | 748 | no change |
| 7 Aug 2026, 07:17 | 748 | first reading |
10 posts held, back to 5 August 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
347 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 31.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357265201114682907 | 110 | 31.7% | |
| custom 5404451992456156919 | 56 | 16.1% | |
| custom 5339262828513631215 | 49 | 14.1% | |
| custom 5404398915250332921 | 49 | 14.1% | |
| custom 5355073028331964240 | 42 | 12.1% | |
| custom 5355334089329115979 | 41 | 11.8% |
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 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 347 reactions 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 5 August 2026 to 7 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @seultown. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 10 most recent posts we hold for this entry, published 5 August 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Здравствуйте! Мы бы хотели поделиться с вами нашим танцевальным кавером на ‘Surfin’ Boy’ 🤍 Надеемся на вашу поддержку, спасибо! https://youtu.be/UiCkTLbWokI?si=vTRFaTQt0ORIkW14
custom 53572652011146829076custom 54043989152503329212
и куда мы таким составом
custom 535533408932911597915custom 54044519924561569198custom 54043989152503329216custom 53550730283319642405custom 53392628285136312153custom 53572652011146829072
фанчант почти перекрикивает музыку… oh red velvet you’re forever LOVED and CHERISHED!
custom 533926282851363121520custom 535726520111468290712custom 54043989152503329219custom 53553340893291159794custom 53550730283319642401
RED VELVET - SURFIN' BOY @ MCOUNTDOWN
custom 54043989152503329219custom 53572652011146829077custom 53550730283319642405custom 53553340893291159794custom 53392628285136312151custom 54044519924561569191
wait…
custom 535726520111468290723custom 54043989152503329217custom 53392628285136312153custom 54044519924561569193custom 53550730283319642402
кто-то в твиттере сказал что цвет освещения меняется в соответствии с цветом участницы исполняющей парт… no one as serious as red velvet when it comes to their representative color
custom 540445199245615691922custom 53550730283319642409custom 53572652011146829079custom 53392628285136312155custom 53553340893291159792
YES SIR 🫡 surfin’ boy на studio choom
custom 535726520111468290714custom 53553340893291159797custom 53550730283319642405custom 54044519924561569194custom 53392628285136312151
kind of insane she walks around with a face and body like this
custom 535726520111468290716custom 54043989152503329217custom 53553340893291159796custom 53550730283319642402custom 53392628285136312151
Posted without readable text
custom 540445199245615691918custom 54043989152503329216custom 53550730283319642404custom 53392628285136312153custom 53553340893291159793custom 53572652011146829073
your gym crush @hi_sseulgi just updated her insta-profile 🏃🏻♀️
custom 535726520111468290718custom 533926282851363121512custom 53550730283319642409custom 54043989152503329213
Showing the 10 most recent of 10 posts we hold for @seultown. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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.
@seultown named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“se͟ultown 🏄🏼♀️” (@seultown), 738 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/seultown.
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.