Telegram RegisterThe public register of Telegram
Telegram profile photo for #TEKEHAN_OFFICALL

Channel

#TEKEHAN_OFFICALL

@menteke

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

14subscribers

-1 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-1001752552596
TypeChannel
Username@menteke
Created9 July 2022measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live25 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/menteke

Growth

141514.510 August 2026 — 15 subscribers11 August 2026 — 15 subscribers25 August 2026 — 14 subscribers10 August 202625 August 2026
3 measurements spanning 15 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 14–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:0714-1
11 Aug 2026, 22:3115no change
10 Aug 2026, 00:1615first reading

Engagement

15 posts held, back to 9 July 2022the 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 15 posts for this entry, the most recent from 3 May 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 May 2023, 15:16 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.

19 Jan 2023, 00:03 UTC264 viewsread 11 August 2026

156 amerika 500 tmt 215 amerika 1600 tmt 69 ameriak 1400 tmt 67 ameriak 2000 tmt 31 turk 1400 tmt 45 afhanistan 1750 tmt

8 Jan 2023, 15:51 UTC289 viewsread 11 August 2026

Kompyutere iPhone Macbook Android lyubou ocmeyan vpnler Arzanlady🙈 250 tmt problemasyz isleya 5 adamlyk aljakjaklara skidka 700 tmt 👍 Aljaklar @tekehan1 (1AY BEZ BLOK İSHLEYA✅)

26 Nov 2022, 04:46 UTC310 viewsread 11 August 2026

Vps bar yurt Amerika baha 900 tmt ylalašyk ba garantiya 100 % Halal gorišip bolya aljaklar licka @tekehan1

24 Aug 2022, 20:10 UTC412 viewsread 11 August 2026

Men barada yene maglumat gerek bolsa✅ Marydan ✔️ marylylar ya mara gelenler habarlasyn lyuboy vremya gorusup bolya Lickam @tekehan1

22 Aug 2022, 10:38 UTC555 viewsread 11 August 2026

OZIM BARADA - MEN MASENNIK DAL❌ GORIPLEM OZLERI MASENIK DIYIP SURAT YASAYA WE GORIPCILIK ETYAR @Owner_by_telegram Dakazat elinde yok prosta masennik dp goyan bolya 😂🤦 Suratlary men dal 😂❌ suratym gerek bolsa insta - #kuvvat_saparov_tekehan

Showing the 12 most recent of 15 posts we hold for @menteke. 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 — 681,370 of 1,625,954entries 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“#TEKEHAN_OFFICALL” (@menteke), 14 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/menteke.

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.