Telegram RegisterThe public register of Telegram
Telegram profile photo for OFC PARTNERSHIP DELIVERY ROLEPLAYER'S

Channel

OFC PARTNERSHIP DELIVERY ROLEPLAYER'S

@OFCPartnershipPaketanRoleplayers

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · 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-1001292680358
TypeChannel
Username@OFCPartnershipPaketanRoleplayers
Created21 March 2021 — measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 November 2026
Measurements held2
On Telegramt.me/OFCPartnershipPaketanRoleplayers

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 72% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@PartnershipPaketanRoleplayersOfc/2620 Mar 2021, 08:25 UTC@OFCPartnershipPaketanRoleplayers/5 · this entry21 Mar 2021, 13:05 UTC1.0029 hours
@PartnershipPaketanRoleplayersOfc/2720 Mar 2021, 08:25 UTC@OFCPartnershipPaketanRoleplayers/6 · this entry21 Mar 2021, 13:05 UTC1.0029 hours
@PartnershipPaketanRoleplayersOfc/2920 Mar 2021, 08:26 UTC@OFCPartnershipPaketanRoleplayers/10 · this entry21 Mar 2021, 14:19 UTC1.0030 hours
@PartnershipPaketanRoleplayersOfc/3425 Mar 2021, 10:06 UTC@OFCPartnershipPaketanRoleplayers/15 · this entry25 Mar 2021, 10:10 UTC1.004 minutes
@PartnershipPaketanRoleplayersOfc/3525 Mar 2021, 10:15 UTC@OFCPartnershipPaketanRoleplayers/16 · this entry25 Mar 2021, 10:15 UTC1.00under a minute
@PartnershipPaketanRoleplayersOfc/2520 Mar 2021, 08:25 UTC@OFCPartnershipPaketanRoleplayers/4 · this entry21 Mar 2021, 13:05 UTC0.9929 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@PartnershipPaketanRoleplayersOfc7 (7/7 hand-verifiable sample passed)1.0029 hours@PartnershipPaketanRoleplayersOfc (7–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 7 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 21 March 2021 to 25 April 2021. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @PartnershipPaketanRoleplayersOfc. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

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, 08:151no change
7 Aug 2026, 00:181first reading

Engagement

19 posts held, back to 21 March 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 19 posts for this entry, the most recent from 25 April 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
4

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

25 Apr 2021, 04:07 UTC91 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ DELIVERY ROLEPLAYER'S 57.) Nama Channel : ʚ bαbเᧉs cαstᥣᧉ ɞ Username Channel : @BABBIESCASTLE Bot Official : @BABIESCASTLEBOT Bot mp / ps : @babiescastle_bot 58.) nama ch : AREA 381% username ch : @AREAZ381 bot aktif : @official381bot 59.) nama ch : OFC SIRAJA GANK username ch : @ofcsrjgank bot mp/ps : @mpssirajagankbot status ch : aktif 60.) nama : MARKAS KTH usn : @ofcmar…

23 Apr 2021, 18:23 UTC83 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ DELIVERY ROLEPLAYER'S 30.) nama channel : OFC. BARAXY GANK username channel : @baraxygank bot mp ps : @Baraxyptspbot PJ: @JENNIERUBYJANEW 31.) OTTO CITY id ch : @otto_city Bot MPPS : @Ottocitympps_bot 32.) nama channel : BARAJA username channel : @BARAJAOFC bot mpps : @PARTNERBRJBOT status ch : AKTIF 33.) nama channel : 𝕭𝐈𝐒𝐌∆𝕽𝐂𝐊 𝐆∆𝐍𝐊 username channel : @BismarckGank bot akti…

23 Apr 2021, 14:41 UTC76 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ DELIVERY ROLEPLAYER'S 1.) Nama Channel: WAW SQUAD Username Channel: @WAWSQ Username Bot Official: @WAWSQBOT Status : rombak sub unit Nama channel : FAIRY ORGANIZER Username Channel : @FAIRYORGANIZER status : aktif Username Bot Official: @WAWSQBOT Status : aktif 2.) nama channel : OFC. BARAXY GANK username channel : @baraxygank bot mp ps : @Baraxyptspbot PJ: @JENNIERUBYJANEW […

26 Mar 2021, 01:05 UTC168 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ 𝐏𝐀𝐊𝐄𝐓𝐀𝐍 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑𝐒 288.) Nama Channel : Nongki Promote Username Channel : @NONGKIPROMOTE Username Bot : @partnernongkibot Status Ch : Aktif 289.) ❍ Nama Channel : MΛRΛXΣS GΛNK ❍ Username Channel : @ofcmaraxesgank ❍ Bot Mpps : @MRXSMPPSBOT ❍ Status Channel : Aktif ❍ Penanggung Jawab : @Notyourenjun & @Notrealjisoo 290.) Nama Channel : ANTONIUS HOSPITAL Username Channel : @Antoni…

25 Mar 2021, 10:28 UTC131 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ 𝐏𝐀𝐊𝐄𝐓𝐀𝐍 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑𝐒 257.) nama channel : O F C - 𝑨𝑹𝑮𝑶𝑺 𝑩𝑳𝑨𝒁𝑬 username channel : @argsblazex nama channel mpps : 𝑨𝑹𝑮𝑶𝑺 𝑩𝑳𝑨𝒁𝑬 PARTNERSHIP username channel mpps : @argsblazepartnership 258.) nama ch : TASKALA GANK id : @taskalagank bot ps : @mppstaskalabot status ch : rombak 259.) ⛓️CHANNEL’s NAME : GRACIOUS PROMOTE GET EDITING GUEST STAR RP GOTAS GANG GHEFAISTOS LETAK RASA GIDEO…

25 Mar 2021, 10:22 UTC87 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ 𝐏𝐀𝐊𝐄𝐓𝐀𝐍 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑𝐒 257.) nama channel : O F C - 𝑨𝑹𝑮𝑶𝑺 𝑩𝑳𝑨𝒁𝑬 username channel : @argsblazex nama channel mpps : 𝑨𝑹𝑮𝑶𝑺 𝑩𝑳𝑨𝒁𝑬 PARTNERSHIP username channel mpps : @argsblazepartnership 258.) nama ch : TASKALA GANK id : @taskalagank bot ps : @mppstaskalabot status ch : rombak 259.) ⛓️CHANNEL’s NAME : GRACIOUS PROMOTE GET EDITING GUEST STAR RP GOTAS GANG GHEFAISTOS LETAK RASA GIDE…

25 Mar 2021, 10:15 UTC73 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ 𝐏𝐀𝐊𝐄𝐓𝐀𝐍 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑𝐒 (227.) Nama Channel : Official Mas & Official Adek Username Channel : @OfcMas & @OfcAdek Official Bot : @MasDekMpsBot 228.) Nama Channel : 𝐑𝐈𝐕𝐀𝐙𝐊𝐀 𝐇𝐎𝐆𝐖𝐀𝐑𝐓𝐒 𝐀𝐂𝐀𝐃𝐄𝐌𝐘 Usn channel : @comeonoverhere Bot : @xrivaz_bot @rivazxka_bot 229.) nama ch : OFC JEN₲₲ALA username ch : @ofcjenggala bot yang aktif : @Jenggalaabot bot mp/s. : @jenggalampps_bo…

25 Mar 2021, 10:10 UTC57 viewsread 14 August 2026

╔࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╗ 𝐏𝐀𝐊𝐄𝐓𝐀𝐍 𝐑𝐎𝐋𝐄𝐏𝐋𝐀𝐘𝐄𝐑𝐒 (226.) Nama Channel : PERMAISOERI Username Channel : @PERMAI5OERI Username Bot : @permaisoeribot ╚࿇══━━ೋ˚*•̩̩͙✩•̩̩͙*˚ೋ━━══࿇╝ ©®: Utama 1: @PartnershipPaketanRoleplayersOFC Utama 2: @OFCPartnershipPaketanRoleplayers ▌│█║▌║▌║ ▌║▌║█│ ▌│█║▌║▌█

21 Mar 2021, 14:19 UTC95 viewsread 14 August 2026

Ⓟⓐⓡⓣⓝⓔⓡⓢⓗ ⓘ Ⓟ_ ⅌ᥲkꫀtᥲᥒ Ꭱꪮᥣꫀρᥣᥲᥡꫀɾ'᥉ : ©® : @PartnershipPaketanRoleplayersOFC

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

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.

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.

“OFC PARTNERSHIP DELIVERY ROLEPLAYER'S” (@OFCPartnershipPaketanRoleplayers), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/OFCPartnershipPaketanRoleplayers.

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.