Telegram RegisterThe public register of Telegram

Channel

ROUGWORK PARTNERSHIP

@rougworkpartnership

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

2subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001581077323
TypeChannel
Username@rougworkpartnership
CreatedBetween 1 July 2021 and 16 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/rougworkpartnership

Growth

212 Aug 2026, 22:53 — 2 subscribers13 Aug 2026, 19:32 — 2 subscribers12 Aug 2026, 22:5313 Aug 2026, 19:32
2 measurements taken within a single day. 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 19:322no change
12 Aug 2026, 22:532first reading

Engagement

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

Recent posts

6 Aug 2021, 03:32 UTC54 viewsread 13 August 2026

꒦꒷ PAGE 13 주 O1. ⌨︎ MΛLΛƘΛ 🇱🇰 usn ch : @OFCMALAKKA bot aktif : @psmalakabot O2. ⌨︎ WARKOP GHOSTING OFC. usn ch : @warkopghosting bot aktif : @Archivempps_bot O3. ⌨︎ usn ch : bot aktif : O4. ⌨︎ usn ch : bot aktif : O5. ⌨︎ usn ch : bot aktif : O6. ⌨︎ usn ch : bot aktif : O7. ⌨︎ usn ch : bot aktif : O8. ⌨︎ usn ch : bot aktif : O9. ⌨︎ usn ch : bot aktif : 1O. ⌨︎ usn ch : bot aktif :

3 Aug 2021, 05:15 UTC43 viewsread 13 August 2026

꒦꒷ PAGE 12 주 O1. ⌨︎ 𝐎𝐅𝐂.蛮 𝐒𝐌𝐀𝐔𝐆 usn ch : @smaugofc bot aktif : @smaugmpps_bot O2. ⌨︎ 𝐎𝐅𝐂 𝟏𝟐𝟗 𝐀𝐑𝐄𝐀 usn ch : @OFC129SQ bot aktif : @SadulanRobot O3. ⌨︎ 𝐎𝐅𝐂 𝐀𝐋𝐄𝐒𝐓𝐑𝐀 分隊 usn ch : @OFCALESTRA bot aktif : @MPPSALESTRA_BOT O4. ⌨︎ ᏒΞΧLΔᗡΞᏒ Usn ch :@rexladerofc bot aktif : @MPPSREXLADER_BOT O5. ⌨︎ RASANA 🇦🇱 usn ch : @ofcrasana bot aktif : @mppsrasana_bot O6. ⌨︎ 𝐑𝐄𝐏𝐔𝐁𝐋𝐈𝐊 𝐉𝐀𝐄𝐇𝐘𝐔𝐍 usn ch : @OFCREPUBLIKJ

1 Aug 2021, 04:52 UTC45 viewsread 13 August 2026

꒦꒷ PAGE 11 주 O1. ⌨︎ 𝐃𝐄𝐒𝐀 𝐉𝐄𝐍𝐍𝐈𝐄 usn ch : @DESAJNNIE bot aktif : @DESJENPSBOT O2. ⌨︎ 6:1 𝐌∅TORCYCLE 🇳🇿 usn ch : @OFC61MC bot aktif : @PS61MCbot O3. ⌨︎ 𝐏𝐇ӨΣ𝐍𝐈𝐗 𝐌𝐎𝐎𝐍 usn ch : @OFCPHOENIXMOON bot aktif : @PHOENIXMMPPS_BOT O4. ⌨︎ SUGAR TAENNIE usn ch : @SUGARTAENNIEOFC bot aktif : @taenniepsbot O5. ⌨︎ 𝐎𝐅𝐂 𝐃𝐀𝐄𝐑𝐀𝐇 𝐊𝐓𝐇 usn ch : @drkthrpw bot aktif : @mppsdrkthbot O6. ⌨︎𝐎𝐅𝐂. 𝐋𝐎𝐊𝐀𝐋𝐀𝐍 𝐇𝐘𝐁𝐄 🕰 usn ch :

1 Aug 2021, 04:52 UTC35 viewsread 13 August 2026

꒦꒷ PAGE 1O주 O1. ⌨︎ 𝗔𝗥𝗘𝗔 𝗧𝗔𝗘𝗡𝗡𝗜𝗘 usn ch : @OFCAREATAENNIE bot aktif : @TNJNAREAPSBOT O2. ⌨︎ KOMPLEK JAVJENSOO usn ch : @KOMPLEKJAVJENSOO bot aktif : @MPPSJVJS327BOT O3. ⌨︎ 𝐎𝐅𝐂 𝕶𝐈𝐋𝐋𝐄𝐑 𝕾𝐇𝐎𝐋𝐃𝐈𝐄𝐑 usn ch : @OFCKILLERSHOLDIER bot aktif : @MPPSKSD_BOT O4. ⌨︎ 𝐒𝐇𝐎𝐋𝐌𝐀𝐓𝐄 𝐎𝐑𝐆𝐀𝐍𝐈𝐙𝐄𝐑 usn ch : @SHOLMATERORGANIZER bot aktif : @SMOMPPS_BOT O5. ⌨︎ 𝐎𝐅𝐂. 𝐏𝐎𝐋𝐀𝐑𝐈𝐒 𝐆𝐀𝐍𝐊 🇸🇴 usn ch : @ofcpolarisgnk bot aktif : @ofcp

1 Aug 2021, 04:52 UTC23 viewsread 13 August 2026

꒦꒷ PAGE O9 주 O1. ⌨︎ 𝐎𝐅𝐂 𝕭𝐔𝐑𝐑𝐎𝐖𝐇𝐎𝐏𝐒 usn ch : @BURROWHOPS bot aktif : @mppsbrwrobot O2. ⌨︎ 𝐎𝐅𝐂 𝐁𝐑𝐈𝐌𝐎𝐁 usn ch : @brmbofc bot aktif : @psbrimob_bot O3. ⌨︎ IMPERIUM DJAVU usn ch : @djavuimperium bot aktif : @imperiumdjavu_bot O4. ⌨︎ 𝐕𝐎𝐔𝐑𝐆𝐈𝐄𝐙 usn ch : @VGZOFC bot aktif : @Mppsvgzbot O5. ⌨︎ KOMPLEK JAVJENSOO usn ch : @KOMPLEKJAVJENSOO bot aktif : @mppsjvjsbot O6. ⌨︎ VOLORIOUS SQ OFC usn ch : @VOLO

1 Aug 2021, 04:51 UTC17 viewsread 13 August 2026

꒦꒷ PAGE O8 주 O1. ⌨︎ 𝐓𝐎𝐍𝐆𝐊𝐑𝐎𝐍𝐆𝐀𝐍 𝐊𝐉𝐇 usn ch : @OFCTKJH bot aktif : @MPPSTKJH_BOT O2. ⌨︎ BLACKPHANTOM usn ch : @BLACKPHANTOMOFC bot aktif : @BLACKPHANTOMOFCBOT O3. ⌨︎ Ø𝐅𝐂 𝐓𝐎$𝐀𝐒𝐈 usn ch : @OFCTOSASI bot aktif : @Tosasirobot O4. ⌨︎ INTELIJEN usn ch : @INTELIJENOFC bot aktif : @INTELIJENMPSBOT O5. ⌨︎ MISTER KTH usn ch : @OFCMISTERKTH bot aktif : @MPMTRKTHBOT O6. ⌨︎ 𝐎𝐅𝐂 𝐏𝐀𝐒𝐔𝐊𝐀𝐍 𝐊𝐓𝐇 usn ch : @OFCP

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

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

“ROUGWORK PARTNERSHIP” (@rougworkpartnership), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/rougworkpartnership.

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.