Telegram RegisterThe public register of Telegram
Telegram profile photo for Padre Juan Razo

Channel

Padre Juan Razo

@PadreJuanRazo

Has discussion group

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

2,735subscribers

-49 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002188624798
TypeChannel
Username@PadreJuanRazo
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/PadreJuanRazo

Topic

Religion — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

2,7352,7842,759.57 August 2026 — 2,784 subscribers8 August 2026 — 2,782 subscribers11 August 2026 — 2,777 subscribers15 August 2026 — 2,772 subscribers18 August 2026 — 2,769 subscribers20 August 2026 — 2,765 subscribers24 August 2026 — 2,762 subscribers28 August 2026 — 2,760 subscribers31 August 2026 — 2,755 subscribers3 September 2026 — 2,749 subscribers9 September 2026 — 2,742 subscribers12 September 2026 — 2,741 subscribers13 September 2026 — 2,741 subscribers16 September 2026 — 2,735 subscribers7 August 202616 September 2026
14 measurements spanning 39 days, net -49. 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 2,728–2,791 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 06:562,735-6
13 Sept 2026, 14:392,741no change
12 Sept 2026, 23:212,741-1
9 Sept 2026, 00:222,742-7
3 Sept 2026, 15:202,749-6
31 Aug 2026, 02:532,755-5
28 Aug 2026, 00:462,760-2
24 Aug 2026, 20:472,762-3
20 Aug 2026, 23:582,765-4
18 Aug 2026, 10:382,769-3
15 Aug 2026, 07:472,772-5
11 Aug 2026, 13:132,777-5
8 Aug 2026, 16:112,782-2
7 Aug 2026, 20:462,784first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Padre Juan Razo” (@PadreJuanRazo), 2,735 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/PadreJuanRazo.

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.