Telegram RegisterThe public register of Telegram
Telegram profile photo for PC INFO

Channel

PC INFO

@pelangipulsajember

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

111subscribers

-5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001130604808
TypeChannel
Username@pelangipulsajember
CreatedBetween 1 June 2017 and 20 October 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 7 October 2026
On Telegramt.me/pelangipulsajember

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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 why it has no browse page of its own yet.

Growth

111116113.56 August 2026 — 116 subscribers9 August 2026 — 116 subscribers12 August 2026 — 115 subscribers4 September 2026 — 113 subscribers25 September 2026 — 111 subscribers6 August 202625 September 2026
5 measurements spanning 50 days, net -5. 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 110–117 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 09:38111-2
4 Sept 2026, 04:01113-2
12 Aug 2026, 13:14115-1
9 Aug 2026, 05:16116no change
6 Aug 2026, 02:45116first reading

Engagement

20 posts held, back to 20 October 2018 — 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 28 November 2018. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Nov 2018, 22:37 UTC≈5,470 viewsread 9 August 2026

ARIK KRISTANTO PENIPU PELANGI PULSA BERIKUT KLARIFIKASINYA: REKENING KAMI DI BAWAH INI ADALAH REKENING SERVER BCA: 0244184321 MANDIRI: 1430013378672 BRI: 057701024596509 BNI: 337790711 A/N: ARIK KRISTANTO DILARANG KERAS menggunakan Rekening untuk kebutuhan selain order SALDO Member Pelangi Pulsa. Saat ini marak modus penipuan online menggunakan rekening server untuk bertransaksi. Kami tegaskan bahwa itu adalah …

12 Nov 2018, 01:17 UTC325 viewsread 9 August 2026
Forwarded from @pelangipulsanew

@pelangipulsanew chanel kami ya

2 Nov 2018, 22:06 UTC283 viewsread 9 August 2026
Forwarded from @pelangipulsanewPhoto

Photo, posted without a caption

2 Nov 2018, 22:06 UTC229 viewsread 9 August 2026
Forwarded from @pelangipulsanew

Bismillahirrohmairrohim Assalamualaikum warohmatullahi wabarokatu Mohon doa dan bantuannya untuk meringankan biaya penyembuhan saudara kita MILATUL MAFTAH yang sedang berjuang melawan penyakit (GBS) *Guillain Barre Syndrome* dan membutuhkan biaya yang tidak sedikit. Mila ini adalah mahasiswa dari program bidikmisi. Orang tua laki-laki bekerja sebagai pedagang dan ibunda sebagai ibu rumah tangga. Saudara mila saat i…

24 Oct 2018, 12:52 UTC111 viewsread 9 August 2026
Forwarded from @pelangipulsanew

INPUT VOUCHER AXIS DAN XL GANGGUAN YAAA

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“PC INFO” (@pelangipulsajember), 111 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/pelangipulsajember.

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.