Telegram RegisterThe public register of Telegram
Telegram profile photo for союзы лояльти

Channel

союзы лояльти

@hamiunion

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

2subscribers

+1 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-1003787230024
TypeChannel
Username@hamiunion
Created29 January 2026 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live28 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 28 September 2026
On Telegramt.me/hamiunion

Growth

121.58 August 2026 — 1 subscribers14 August 2026 — 1 subscribers10 September 2026 — 2 subscribers8 August 202610 September 2026
3 measurements spanning 34 days, net +1. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 22:202+1
14 Aug 2026, 22:481no change
8 Aug 2026, 10:011first reading

Engagement

18 posts held, back to 29 January 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 18 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 11:39 UTC5 viewsread 14 August 2026

добрый день. заключим союз? канал: @ASTREVAL_FM след: @ANITD пдп 11:11 папка: актив, актив+рп, вз допы: 2:2 @NNDUII 3:3 @zxcursebq 4:4 @Hikewen 5:5 @skel3tonz 6:6 @ABVMXN 7:7 @RXGHP 8:8 @OTHDN1 9:9 @rtv3n 10:10 @NUARE7 11:11 @xhiroks

8 Aug 2026, 11:39 UTC5 viewsread 14 August 2026

здравствуйте, не против союза? с вашими правилами ознакомлена, посты на рп кидайте в лс, пост с нас/двух сторон папки: актив+рп, рп пдп: 1:1 онли правила — связь @ahXXXegao хочу заключить с лояльти

8 Aug 2026, 09:03 UTC5 viewsread 14 August 2026

канал: @nekoworld4u след: @bxsourae папка: рп допы:@AY4UN @kaw4iihentai @KanekiHeartBreaking @blessseed67

2 Aug 2026, 21:41 UTC10 viewsread 14 August 2026

здравствуйте, давайте заключим союз 3:3 ? с @L0Y44LTY правила канал: @excc1se папка: рп след: @Qw1d_s 2:2 — @DevvGF 3:3 — @ADNLKD

29 Jul 2026, 14:12 UTC14 viewsread 14 August 2026

Здравствуйте, хочу предложить вам сотрудничество. канал - @AUGURSFM след - @TR7ISS папка рп Правила: обязательно к прочтению. допы: 2:2 @waldhub 3:3 @AHTROJ 4:4 @FQ7ZA

19 Jul 2026, 11:49 UTC26 viewsread 14 August 2026

Канал: @CONTINTL След: @SCHayA Допы: 2:2 @asp1ld 3:3 @V1GG0M7 4:4 @XXSWEP

19 Jul 2026, 11:49 UTC25 viewsread 14 August 2026

3:3 След: @MJ69EVIL Канал: @snakes_empire02 Папка: вз. Доп 1: @FAb1Noo Доп 2: @jnght

11 Jul 2026, 14:08 UTC33 viewsread 14 August 2026

Канал: @HB_KROWFORD След: @SEX_MORT Пдп: 4:4 Папка: рп Допы: 1:1 @SEX_MORT 2:2 @M01MIMI 3:3 @Viiincyyy 4:4 @xxsm6

11 Jul 2026, 14:07 UTC32 viewsread 14 August 2026

здравствуйте, хочу предложить лояльти сотрудничество с @SUCCUBfm ☺ макс пдп 4:4 папка рп/вз/рп+актив правила @UnsRls след @TrueTaesanGf допы: 2:2 @PydeuNouw 3:3 @TrueBeomgyuGf 4:4 @n1kssz

11 Jul 2026, 14:07 UTC32 viewsread 14 August 2026

канал - @NexoraFm След - @MakeTroll1 папка - рп пдп - 2:2 допы: 2:2 @VIVGIK

11 Jul 2026, 14:06 UTC32 viewsread 14 August 2026

Здравствуйте. Я хотела бы заключить союз с @L0Y44LTY. Надеюсь, нам удастся заключить данный союз. Канал:@succubus_kf Следящий:@time_killer60 Папка: рп пдп:4:4 Допы:@MIA_GJ @F9LSD @LluVrr

Showing the 12 most recent of 18 posts we hold for @hamiunion. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“союзы лояльти” (@hamiunion), 2 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/hamiunion.

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.