Telegram RegisterThe public register of Telegram

Channel

PS TABEN VILLAGE

@TABENVPS

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

1subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001703798357
TypeChannel
Username@TABENVPS
CreatedBetween 1 December 2021 and 7 February 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/TABENVPS

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 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, 12:171no change
7 Aug 2026, 01:371first reading

Engagement

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

Recent posts

15 Jul 2026, 12:20 UTCviews —

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

5 Jul 2026, 10:29 UTCviews —

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

14 Feb 2022, 11:26 UTC60 viewsread 14 August 2026

╭──────╯•╰──────╮ 𖤍 PAGE 21 𖤍 ╰──────╮•╭──────╯ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ 01. OFC NEOITZY •✎ @neoitzysq •✎ @mppsneoitzy_bot ─────────────── 02. NÆVIZT •✎ @naevizt •✎ @mppsnaeviztbot ─────────────── 03. MĀRVELOCE •✎ @OFCMARVELOCE •✎ @MPPSMARVELOCEBOT ─────────────── 04. •✎ •✎ ─────────────── 05. RAPLINE •✎ @OFCRAPLINE •✎ @RAPHYBEPSBOT ─────────────── 06. 𝗔𝗥𝗧𝗜𝗙𝗜𝗖𝗜𝗔𝗟 𝗪𝗢𝗥𝗟𝗗 𝗭 •✎ @OFCARFINICW •✎ @AWZMP2SBO

8 Feb 2022, 04:31 UTC73 viewsread 14 August 2026

╭──────╯•╰──────╮ 𖤍 PAGE 20 𖤍 ╰──────╮•╭──────╯ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ 01. 𝐎𝐅𝐂 𝐂𝐎𝐑𝐍𝐄𝐑𝐕𝐀 •✎ @OFCCORNERVA •✎ @mppscrnv_bot ─────────────── 02. 𝐀𝐑𝐆𝐄𝐒𝐓Ø𝐃 𝐒𝐐 •✎ @ARGESTODSQ •✎ @agtmpps_bot ─────────────── 03. NEOZONEKIDZY_9 •✎ @OFCNZKY9 •✎ @mppsnzky9_bot ─────────────── 04. 𝟳𝟵𝟱. 𝗟𝗢𝗥𝗗 𝗞𝗧𝗛 ✦ •✎ @kthlordofc •✎ @ldkthmppsbot ─────────────── 05. OFC V.I.P •✎ @VIPSQUADD •✎ @MPPSVIPBOT ─────────────── 06. OFC

7 Feb 2022, 12:48 UTC42 viewsread 14 August 2026

╭──────╯•╰──────╮ 𖤍 PAGE 19 𖤍 ╰──────╮•╭──────╯ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ 01. 𝐃𝐒𝐕 𝐏𝐑𝐎𝐌𝐎𝐓𝐄 •✎ @domsubvillage •✎ @mppsdomsubvillage_bot ─────────────── 02. 189 KOMPLOTAN KTH •✎ @OFCKPKTH •✎ @pskopkthbot ─────────────── 03. 𝐎𝐅𝐂. 𝑳𝖆 𝑽𝖎𝖊 𝐒𝐐 •✎ @OFCLVSQ •✎ @LaViepartner_bot ─────────────── 04. REPUBLIC SUGA •✎ @REPUBLICSUGA •✎ @MPPSREPSUGA_BOT ─────────────── 05. OFC KAMPUNG COGAN •✎ @KCGANK •✎ @mppskcg_bot

7 Feb 2022, 12:46 UTC29 viewsread 14 August 2026

╭──────╯•╰──────╮ 𖤍 PAGE 18 𖤍 ╰──────╮•╭──────╯ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ 01. OFC BLONDSÉ •✎ @OFCBLONDSE •✎ @mppsrosebot [SUB UNIT] • MOMMY SEUX •✎ @MOMSEUX •✎ @mppsrosebot ─────────────── 02. Higeia Hospital •✎ @HOSPITALHIGEIA •✎ @mppshigeiabot ─────────────── 03. 𝟮𝟲𝟴. 𝗣𝗢𝗝𝗢𝗞 𝗡𝗚𝗢𝗣𝗜 •✎ @OFCPOJOKNGOPI •✎ @pongompps_bot ─────────────── 04. 𝐎𝐅𝐂 𝐈𝐍𝐃𝐄𝐒𝐓𝐑𝐔𝐂𝐓𝐈𝐁𝐋𝐄 •✎ @OFCINDESTRUCTIBLE •✎ @KAWANIDTBOSTBOT [SUB U

7 Feb 2022, 12:46 UTC22 viewsread 14 August 2026

╭──────╯•╰──────╮ 𖤍 PAGE 17 𖤍 ╰──────╮•╭──────╯ ▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂▂ 01. 𝑪ITIEZ 92 •✎ @citiez92 •✎ @Mppscitiezbot [SUB UNIT] • 𝐎𝐅𝐂 𝐌𝐀𝐑𝐊𝐇𝐘𝐔𝐂𝐊 •✎ @ofcmarkhyuckcity62 •✎ @Mppscitiezbot ─────────────── 02. 𝐎𝐅𝐂 𝐂𝐀𝐒𝐓𝐋𝐄 𝐏𝐇𝐀𝐍𝐓𝐄𝐑𝐀 𝐋𝐄𝐎 •✎ @PhanteraLeoOFC •✎ @PARTNERSHIPPANTHERABOT ─────────────── 03. CENTRÈVILLE ACADEMY •✎ @centrevilleacademy •✎ @mppscentrevbot [SUB UNIT] • Panku Promote •✎ @pankupromote •✎ @

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

“PS TABEN VILLAGE” (@TABENVPS), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/TABENVPS.

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.