Channel
@swiftietimes
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
861subscribers
-23 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002009485097 |
|---|---|
| Type | Channel |
| Username | @swiftietimes |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/swiftietimes |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 04:21 | 861 | -7 |
| 4 Sept 2026, 19:00 | 868 | -1 |
| 27 Aug 2026, 19:42 | 869 | -7 |
| 19 Aug 2026, 20:03 | 876 | -6 |
| 13 Aug 2026, 13:06 | 882 | -1 |
| 7 Aug 2026, 01:36 | 883 | -1 |
| 6 Aug 2026, 17:30 | 884 | no change |
| 6 Aug 2026, 17:20 | 884 | first reading |
9 posts held, back to 14 July 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 9 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
330 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 38.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💋 | 128 | 38.8% | |
| 💘 | 78 | 23.6% | |
| custom 5269536010148018441 | 55 | 16.7% | |
| custom 5269289573514517712 | 49 | 14.8% | |
| custom 5251482033514909661 | 20 | 6.06% |
Custom emoji. 3 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 9 of the 9 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 330 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 14 July 2026 to 28 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.
💋карли клосс о свадьбе тейлор и трэвиса: «послушайте, я стараюсь защищать приватность личной жизни своих друзей, но что я могу сказать, так это то, что они потрясающая пара, и я очень за них рада.»
💘16💋7custom 52695360101480184414custom 52692895735145177123custom 52514820335149096612
taydaughter from hell ❤️👴
💘15custom 526928957351451771210custom 52695360101480184416💋3custom 52514820335149096611
🇪🇸🇪🇸
💋36custom 526953601014801844110💘9custom 52514820335149096612custom 52692895735145177122
are you ready for it? 🇪🇸 🇦🇷 будете смотреть финал чемпионата мира по футболу? за кого болеете?
💋15💘5custom 52695360101480184414custom 52514820335149096612custom 52692895735145177121
еще одна фотография со свадьбы💋
custom 526928957351451771219💋7custom 52514820335149096613💘2custom 52695360101480184412
современные певицы как диснеевские принцессы. ♡ ࿔‧ ֶָ֢˚˖ my sabrina carpenter ˖˚ֶָ֢ ‧࿔
custom 526953601014801844115💋4custom 52692895735145177122custom 52514820335149096611
больше фотографий с тейлор со свадьбы лоры крук 🤩
💋26💘6custom 52695360101480184416custom 52514820335149096613custom 52692895735145177122
🌼карли клосс и эсте хайм посетили концерт Jay-Z на стадионе yankee
💋21custom 52695360101480184416custom 52692895735145177124custom 52514820335149096613💘1
vogue поделились фотографией со свадьбы👼
💘24💋9custom 52692895735145177126custom 52514820335149096613custom 52695360101480184412
Showing the 9 most recent of 9 posts we hold for @swiftietimes. 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.
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.
Named by 12 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“swiftie times 𐙚⊹ ࣪ ˖” (@swiftietimes), 861 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/swiftietimes.
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.