
Supergroup
BETOFFICE GÜNCEL
@betofficeguncel
On this record: Growth · Engagement · Cite this entry
6,732members
-223 since we began measuring on 7 August 2026
127 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002049385189 |
|---|---|
| Type | Supergroup |
| Username | @betofficeguncel |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/betofficeguncel |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 31 Aug 2026, 18:27 | 6,732 | -32 |
| 28 Aug 2026, 10:57 | 6,764 | -30 |
| 27 Aug 2026, 21:20 | 6,794 | no change |
| 25 Aug 2026, 15:23 | 6,794 | -33 |
| 22 Aug 2026, 11:26 | 6,827 | -24 |
| 18 Aug 2026, 16:14 | 6,851 | -28 |
| 15 Aug 2026, 10:06 | 6,879 | -32 |
| 11 Aug 2026, 19:52 | 6,911 | -34 |
| 8 Aug 2026, 12:47 | 6,945 | -10 |
| 7 Aug 2026, 12:43 | 6,955 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“BETOFFICE GÜNCEL” (@betofficeguncel), 6,732 members as measured 31 August 2026. Telegram Register, tgregister.com/channel/betofficeguncel.
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.