Channel
SPIRITUAL KNOWLEDGE
@Christian_spritualknowledge
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,905subscribers
+11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001122769879 |
|---|---|
| Type | Channel |
| Username | @Christian_spritualknowledge |
| Created | Between 1 June 2017 and 31 March 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/Christian_spritualknowledge |
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 22 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 18:28 | 1,905 | -1 |
| 5 Nov 2026, 21:27 | 1,906 | +1 |
| 2 Nov 2026, 22:29 | 1,905 | -1 |
| 31 Oct 2026, 02:09 | 1,906 | -3 |
| 27 Oct 2026, 23:27 | 1,909 | +3 |
| 25 Oct 2026, 08:34 | 1,906 | +1 |
| 22 Oct 2026, 14:27 | 1,905 | -2 |
| 19 Oct 2026, 11:06 | 1,907 | +1 |
| 16 Oct 2026, 14:37 | 1,906 | -3 |
| 13 Oct 2026, 11:26 | 1,909 | -1 |
| 7 Oct 2026, 06:38 | 1,910 | +3 |
| 30 Sept 2026, 03:18 | 1,907 | -1 |
| 22 Sept 2026, 01:33 | 1,908 | no change |
| 19 Sept 2026, 11:18 | 1,908 | -1 |
| 14 Sept 2026, 17:58 | 1,909 | -8 |
| 11 Sept 2026, 08:36 | 1,917 | +3 |
| 6 Sept 2026, 14:38 | 1,914 | +2 |
| 30 Aug 2026, 07:57 | 1,912 | +4 |
| 27 Aug 2026, 12:25 | 1,908 | -7 |
| 24 Aug 2026, 08:56 | 1,915 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@bibleverses · 27,562
Telegram ranks this channel #34 of 84 here — alongside 83 others — read 10 September 2026
@Clibraryforyou · 19,254
Telegram ranks this channel #46 of 85 here — alongside 84 others — read 3 October 2026
@pastorvladimirsavchuk · 35,519
Telegram ranks this channel #58 of 88 here — alongside 87 others — read 8 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“SPIRITUAL KNOWLEDGE” (@Christian_spritualknowledge), 1,905 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/Christian_spritualknowledge.
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.