Telegram RegisterThe public register of Telegram
Telegram profile photo for ALL UFS.

Channel

ALL UFS.

@kantomaanji

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

1subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1001585134742
TypeChannel
Username@kantomaanji
Created26 July 2021measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/kantomaanji

Growth

110 August 2026 — 1 subscribers14 August 2026 — 1 subscribers10 August 202614 August 2026
2 measurements spanning 4 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:481no change
10 Aug 2026, 20:451first reading

Engagement

14 posts held, back to 26 July 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 posts for this entry, the most recent from 27 August 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1

Lifetime counters from Telegram’s own channel header, read 14 August 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.

Recent posts

27 Aug 2021, 13:17 UTC658 viewsread 14 August 2026

Sold : vShinichiro Kazutorar imaushil limaushi Kazutoria aHaitani SeisshuInui aImaushi zKawaragi nBrahman Kheisuke xShinsuke

27 Aug 2021, 13:17 UTC659 viewsread 14 August 2026

Beberapa ada yang negotiable, take banyak dapet potongan harga! Contact @PekeJeybot or @matsuwno if you're interested ^____^

27 Aug 2021, 13:17 UTC715 viewsread 14 August 2026

ㅤㅤㅤㅤㅤOthers SEMI ON POINT : @EitaarouOka 5k @EitarouuOka 5k COMMON : 1k/each @Eitharou @vEitarou @tEitarou @Tamakiy @MakiZenind

27 Aug 2021, 13:16 UTC801 viewsread 14 August 2026

ㅤㅤㅤㅤㅤHaikyuu SEMI ON POINT : @ShirabuKenjiroo 10k @AkiiraKunimi 10k @TeruushimaYuji 10k COMMON : @rShirabu 15k

27 Aug 2021, 13:15 UTC895 viewsread 14 August 2026

ㅤㅤㅤㅤㅤTokyo Revengers SEMI ON POINT : @HaaruchiyoSanzu 20k @AkashiHaruchhiyo 20k

27 Jul 2021, 11:00 UTC765 viewsread 14 August 2026
Photo

ㅤㅤㅤㅤㅤREGULATION : i. Payment di awal disertai dengan bukti pembayaran untuk menghindari terjadinya HnR. ii. Booking username max 3 hari dengan DP 30%. Booking tanpa DP max 1 hari. Bila tidak ada kejelasan / unbooked, maka DP akan hangus. iii. Payment via DANA dan Shopeepay. Contact @PekeJeybot / @matsuwno. Jika pesan kamu tidak dibalas dalam 3 jam lebih, silahkan re-chat.

Showing the 12 most recent of 14 posts we hold for @kantomaanji. 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.

Citation-graph rank

Citation-graph rank — 921,327 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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.

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

“ALL UFS.” (@kantomaanji), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kantomaanji.

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.