Telegram RegisterThe public register of Telegram
Telegram profile photo for MAGNETAR · BUG REPORT

Channel

MAGNETAR · BUG REPORT

@magnetarbugreport

On this record: Growth · Engagement · Posts · Cite this entry

69subscribers

-2 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-1001579549000
TypeChannel
Username@magnetarbugreport
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live23 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/magnetarbugreport

Growth

6971707 August 2026 — 71 subscribers9 August 2026 — 71 subscribers23 August 2026 — 69 subscribers7 August 202623 August 2026
3 measurements spanning 16 days, net -2. 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 69–71 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 06:3669-2
9 Aug 2026, 23:1671no change
7 Aug 2026, 07:2871first reading

Engagement

20 posts held, back to 6 June 2025the 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 22 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 May 2026, 18:58 UTC43 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: A22X SUD: MAGISK:30700 API: 34 CPU: MT6833 GPU: MALI-G57 MC2 ISSUE: high battrey consumption REPORTED BY: @Crawler909

17 Mar 2026, 20:49 UTC69 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: ONEPLUS7T SUD: MAGISK:30700 API: 36 CPU: SM8150 GPU: ADRENO™ 640 ISSUE: random reboot to rom bootlogo after using for some times like within 30minutes and then after the random reboot the magnetor dosent work unless i restart the phone i didnt face this issue on infifiy x rom android 16 im facing this issue on derpfest android 16 and evolution x android 16 rom im not u

14 Jan 2026, 20:30 UTC106 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: A05S SUD: MAGISK:30600 API: 35 CPU: KHAJE GPU: ADRENO™ 610 ISSUE: can't activate fastcharge and auto cancel when r runs art command REPORTED BY: @@hadijerr

30 Dec 2025, 18:17 UTC85 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.2.0 (UNIFORM) CDN: APOLLO SUD: MAGISK:30600 API: 33 CPU: SM8250 GPU: ADRENO™ 650 ISSUE: g REPORTED BY: @no

24 Dec 2025, 00:14 UTC84 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: ASUS_X01A_1 SUD: KERNELSU:12164 API: 35 CPU: SDM632 GPU: ADRENO™ 506 ISSUE: bug repport after reinstall REPORTED BY: @Fazza

23 Dec 2025, 22:49 UTC83 viewsread 9 August 2026
File

MAGNETAR+ BUG REPORT VER: 19.6.0-11 (ZULU) CDN: SURYA SUD: KERNELSU:12602 API: 35 CPU: SDMMAGPIE GPU: ADRENO™ 618 ISSUE: test REPORTED BY: @Anonymous

23 Dec 2025, 15:33 UTC70 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: ASUS_X01A_1 SUD: KERNELSU:12164 API: 35 CPU: SDM632 GPU: ADRENO™ 506 ISSUE: when i open game apps its not turn to hame mode but endurance to balance + REPORTED BY: @Fazza

18 Dec 2025, 22:08 UTC68 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: A22X SUD: MAGISK:30600 API: 34 CPU: MT6833 GPU: MALI-G57 MC2 ISSUE: always on extreme mode a REPORTED BY: @crawler909

25 Oct 2025, 21:47 UTC86 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.6.0 (YANKEE) CDN: A04E SUD: MAGISK:29000 API: 34 CPU: MT6765 GPU: POWERVR ROGUE GE8320 ISSUE: --bugreport REPORTED BY: @--bugreport

16 Aug 2025, 05:01 UTC109 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.5.0 (X-RAY) CDN: SUNFISH SUD: KERNELSU:12353 API: 35 CPU: SDMMAGPIE GPU: ADRENO™ 618 ISSUE: appears window that magnetar doesnt respoonnd REPORTED BY: @Anonymous

5 Aug 2025, 00:22 UTC102 viewsread 9 August 2026
File

MAGNETAR BUG REPORT VER: 19.5.0 (X-RAY) CDN: BERYL SUD: KERNELSU:12081 API: 35 CPU: MT6855 GPU: POWERVR B-SERIES BXM-8-256 ISSUE: it keeps stopping REPORTED BY: @lxdkharlo

13 Jul 2025, 15:05 UTC119 viewsread 9 August 2026
File

MAGNETAR+ BUG REPORT VER: 19.5.5 (YANKEE) CDN: CURTANA SUD: UNIDENTIFIED API: 31 CPU: ATOLL-AB GPU: ADRENO™ 618 ISSUE: boss asked REPORTED BY: @Anonymous

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

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

“MAGNETAR · BUG REPORT” (@magnetarbugreport), 69 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/magnetarbugreport.

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.