Telegram RegisterThe public register of Telegram
Telegram profile photo for SwapHub

Channel

SwapHub

@swaphubart

2 usernames

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

640subscribers

+0 since we began measuring on 12 September 2026

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

Register entry

Telegram ID-1002615736019
TypeChannel
Usernames@swaphub @swaphubart
Created13 May 2025measured — dated from the channel’s first post
First recorded12 September 2026
Last confirmed live13 September 2026
Measurements held2
On Telegramt.me/swaphubart

Growth

64012 Sept 2026, 02:47 — 640 subscribers12 Sept 2026, 03:22 — 640 subscribers12 Sept 2026, 02:4712 Sept 2026, 03:22
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 639–641 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 03:22640no change
12 Sept 2026, 02:47640first reading

Engagement

5 posts held, back to 13 May 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 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 5 posts for this entry, the most recent from 31 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 12 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

132 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 30.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52782391729628437224030.3%
custom 52784251364568296562821.2%
custom 52785863394643475491712.9%
custom 5278537260873060117139.85%
custom 5278743273274380516107.58%
75.30%
🥰53.79%
custom 527866248064457199543.03%
👍32.27%
🔥32.27%
🤯21.52%

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

Measured over the 5 most recent posts we hold, published 13 May 2025 to 31 December 2025, 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

31 Dec 2025, 19:54 UTC≈9,640 views63 reactionsread 12 September 2026

С наступающим 2026-м годом! 🥂 Этот год был по-настоящему насыщенным: технологии не стояли на месте, а наше комьюнити росло и становилось всё сильнее. Мы вместе учились создавать идеальные сюжеты, генерировали миллионы уникальных кадров и каждый день доказывали, что грань между воображением и реальностью становится всё тоньше. В новогоднюю ночь принято желать удачи, но мы пожелаем вам абсолютной свободы быть собой.

custom 527842513645682965628custom 527823917296284372216custom 527874327327438051610custom 52785372608730601177custom 52785863394643475492

15 Dec 2025, 18:22 UTC≈10,200 views45 reactionsread 12 September 2026

⚡️ Глобальное обновление платформы: продвинутая генерация, новая валюта и редизайн. Мы рады представить масштабный апдейт приложения. Команда провела большую работу над расширением функционала и гибкостью экономики приложения. Ключевые изменения: ⭐️ Управляемая генерация фото. Качество генерации выведено на новый уровень. Теперь вы не просто запрашиваете фото, а полностью управляете контекстом снимка для текущего п

custom 527823917296284372224custom 527858633946434754911custom 52785372608730601176custom 52786624806445719954

12 Dec 2025, 17:20 UTC≈8,330 views24 reactionsread 12 September 2026

❤️ Всем привет! Мы запускаем закрытый бета-тест грядущего глобального обновления (новая реалистичная генерация фото). Приглашаем всех, кто хочет получить доступ к новым функциям раньше остальных и напрямую повлиять на развитие продукта своим фидбеком. Доступ к бета-версии выдаем через закрытый чат разработчиков. Ссылка на вступление: https://t.me/+5widU3uj7SU2Mjky

7🥰5custom 52785863394643475494👍3🔥3🤯2

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

Mentions

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.

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

“SwapHub” (@swaphubart), 640 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/swaphubart.

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.