Telegram RegisterThe public register of Telegram
Telegram profile photo for Seker's @Maining

Channel

Seker's @Maining

@maining

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2,257subscribers

+1,851 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002343211934
TypeChannel
Username@maining
Created4 February 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live31 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/maining

Growth

4062,2571,331.57 August 2026 — 406 subscribers7 August 2026 — 406 subscribers14 August 2026 — 1,801 subscribers17 August 2026 — 1,852 subscribers20 August 2026 — 2,129 subscribers23 August 2026 — 2,159 subscribers26 August 2026 — 2,172 subscribers29 August 2026 — 2,205 subscribers31 August 2026 — 2,257 subscribers7 August 202631 August 2026
9 measurements spanning 25 days, net +1,851. 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 128–2,535 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 18:342,257+52
29 Aug 2026, 04:332,205+33
26 Aug 2026, 08:322,172+13
23 Aug 2026, 17:052,159+30
20 Aug 2026, 01:322,129+277
17 Aug 2026, 11:351,852+51
14 Aug 2026, 02:071,801+1,395
7 Aug 2026, 05:17406no change
7 Aug 2026, 05:08406first reading

Engagement

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

Recent posts

5 Nov 2025, 00:04 UTC≈3,540 viewsread 7 August 2026

SekerPortal 🏷 Telegram Market: @RareOGs 🏷 Psn Market: @PsnHandles 🪙Public Market: @ProPlaza 📩 Chat: @Faction 🔖 TOS: @SekersTos ❤️ Vouches: @Corroborated Contact: @seker

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

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

“Seker's @Maining” (@maining), 2,257 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/maining.

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.