Telegram RegisterThe public register of Telegram
Telegram profile photo for Our Partnership

Channel

Our Partnership

@bcpunyateman

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-1001702945615
TypeChannel
Username@bcpunyateman
CreatedBetween 1 October 2021 and 13 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live12 September 2026
Measurements held2
On Telegramt.me/bcpunyateman

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 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
15 Aug 2026, 02:451no change
7 Aug 2026, 15:321first reading

Engagement

20 posts held, back to 13 October 2021 — 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 20 posts for this entry, the most recent from 26 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Oct 2021, 05:48 UTC57 viewsread 15 August 2026

líst tєmαn вc 008 ★ : @OFCDARXHORSE ☆ : @mppsdarxhorse_bot ⛥ : aktif ★ : @OFC_ECTROLUX ☆ : @Ectroluxmppsbot ⛥ : aktif ★ : @OFCTAEKOOKHOME ☆ : @MPSHOMEEBOT ⛥ : aktif ★ : @NOBELTRAVELRP ☆ : @Fnpassist_bot ⛥ : aktif ★ : @HYSMTOWN ☆ : @HYSMPSBOT ⛥ : aktif ★ : @AVARELICOFC ☆ : @AVARELICMPPSBOT ⛥ : aktif ★ : @VKOOKSOFC ☆ : @CASTLEPSBOT ⛥ : aktif ★ : @ofctrzyones ☆ : @pstznbot ⛥ : aktif ★ : @OFCKOMPLEKYMJM ☆ : @kmp…

19 Oct 2021, 12:17 UTC46 viewsread 15 August 2026

líst tєmαn вc 007 ★ : @COMICROSE ☆ : @mppsrosebot ⛥ : aktif ★ : @SOSTHINKDULU ☆ : @SHIPTHINK_BOT ⛥ : aktif ★ : @OFCPEISCOS ☆ : @PEISCOSPSBOT ⛥ : aktif ★ : @TERASCINTATMO ☆ : @terascintampps_robot ⛥ : aktif ★ : @BROMMENEO ☆ : @shbtbrommenbot ⛥ : aktif ★ : @OFCHYPERFEST ☆ : @mppshftbot ⛥ : aktif ★ : @FLAYINGWOLFOFC ★ : @OFCARCTICMONKSGANK ☆ : @flarcps_bot ⛥ : aktif ★ : @ENTERPRISEEVENTWO ☆ : @ENTERPRISEMPPS_BOT…

18 Oct 2021, 03:03 UTC34 viewsread 15 August 2026

líst tєmαn вc 006 ★ : @HAKANKTHRPW ☆ : @hakankthmppsbot ⛥ : aktif ★ : @ofcfoevzor ★ : @motomenfess ★ : @alverniahospital ☆ : @mppsfoevzor_bot ⛥ : aktif ★ : @ofcrpolympus ☆ : @Psolympus_bot ⛥ : aktif ★ : @OFCCARVIDAE ☆ : @MPPSDAEROBOT ⛥ : aktif ★ : @OFCENZCT ☆ : @psenztc_bot ⛥ : aktif ★ : @OFCBATALYONN ★ : @ASIANMEDICALCENTER ★ : @ASIANORGANIZERR ☆ : @Partnershipalcbot ⛥ : aktif ★ : @OFCENDEAVOUR ☆ : @MPPSEDVB…

17 Oct 2021, 02:55 UTC33 viewsread 15 August 2026

líst tєmαn вc 005 ★ : @OFCBSNJ ★ : @OFCWPG ☆ : @BSNJMPPS_BOT ⛥ : vakum ★ : @OFCSTRENCZLAND ☆ : @MPPSTRENCZLANDBOT ⛥ : aktif ★ : @BOSSORGANIZER ★ : @BOSSMENFESS ☆ : @MPPSBOSS_BOT ⛥ : aktif ★ : @domsubvillage ☆ : @mppsdomsubvillage_bot ⛥ : aktif ★ : @RAINLINAOFC ☆ : @MPPSREOBOT ⛥ : aktif ★ : @HogwartsBS ☆ : @HobosMpps_bot ⛥ : aktif ★ : @whofallsofficial ☆ : @MPPSWHOFALLSBOT ⛥ : aktif ★ : @CEOFC ☆ : @MPSCARNEV…

16 Oct 2021, 09:56 UTC33 viewsread 15 August 2026

líst tєmαn вc 004 ★ : @OFFICIALBLACKPINKRPW ☆ : @PSBPRPWBOT ⛥ : aktif ★ : @OFC_BRAMANTAS ☆ : @bram_mpps_bot ⛥ : aktif ★ : @OFCBWORLD ☆ : @BTWORLDPSBOT ⛥ : aktif ★ : @OFCALESTRA ☆ : @OFCALESTRA_BOT ⛥ : aktif ★ : @ONLABELSOFFICE ☆ : @ONLABELSMPPSBOT ⛥ : aktif ★ : @moranahspitl ☆ : @Moranahsptlmpps_bot ⛥ : aktif ★ : @ofcdragonvolans ☆ : @ofcmppsdgvbot ⛥ : aktif ★ : @BIDANRP ☆ : @BIDANPARTBOT ⛥ : aktif ★ : @VODX…

16 Oct 2021, 05:13 UTC36 viewsread 15 August 2026

líst tєmαn вc 003 ★ : @ALFARENDRAEO ★ : @ofcalfarendra ☆ : @ALFARENDRAMPPS_BOT ⛥ : aktif ★ : @NEOJOURNEY ☆ : @MPPSJNEOBOT ⛥ : aktif ★ : @arcoirispromote ☆ : @mppsarcoirisbot ⛥ : aktif ★ : @ARGLOVESCH ☆ : @MEDPARTLOVE_BOT ⛥ : aktif ★ : @DARMOGAOFC ★ : @OFCPLAYBOI ☆ : @PACARKITABOT ⛥ : aktif ★ : @AvengersOfc ★ : @NCTZends ☆ : @Sup3rHumanityBot ⛥ : aktif ★ : @HOSPITALGREGORY ★ : @WashingtonsSchool ★ : @ImgLibrary…

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

“Our Partnership” (@bcpunyateman), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/bcpunyateman.

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.