23 Jul 2019, 21:30 UTC≈1,310 viewsread 11 August 2026
File: https://github.com/davtur19/TuriBot/archive/old.zip
Channel
TuriBot Guida
@TuriBotGuida
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
23subscribers
+0 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 | -1001249677293 |
|---|---|
| Type | Channel |
| Username | @TuriBotGuida |
| Description | Guida su come creare un bot usando TuriBot Link GitHub: https://github.com/davtur19/TuriBot By: @davtur19 |
| Created | 26 January 2018 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TuriBotGuida |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:33 | 23 | no change |
| 7 Aug 2026, 05:02 | 23 | first reading |
Engagement
12 posts held, back to 26 January 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 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 12 posts for this entry, the most recent from 23 July 2019. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 7
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
23 Jul 2019, 21:30 UTC≈1,290 viewsread 11 August 2026
La vecchia versione si trova qua https://github.com/davtur19/TuriBot/blob/old/README.md
2 Aug 2018, 18:10 UTC≈1,950 viewsread 11 August 2026
Aggiornamento del bot Ora bisognerà anche settare il nuovo file setup.php. Basta inserire il proprio id e lo username del bot in minuscolo Breve guida aggioranta: https://github.com/davtur19/TuriBot/blob/master/README.md#guida
29 Jan 2018, 21:17 UTC≈1,670 viewsread 11 August 2026
⚠️ Attenzione ⚠️ Il bot genera le variabili in base al contenuto del update, è consigliato leggere attentamente la documentazione (https://github.com/davtur19/TuriBot/blob/master/README.md) e usare bot_debug.php al post di bot.php per capire come funziona o per fare un debug Per fare ciò è necessario sostituire una riga in commands.php, da require_once(bot.php); a require_once(bot_debug.php); ⚠️ Nel file bot_debug.…
27 Jan 2018, 22:25 UTC≈1,030 viewsread 11 August 2026
Gruppo per chi utilizza TuriBot, vuole contribuire o semplicemente vuole capire meglio come funziona: https://t.me/joinchat/AYMflw0vciZoaZi7IVChOg
26 Jan 2018, 04:21 UTC≈1,000 viewsread 11 August 2026
Per capire quali variabili usare, seguire i nomi riportati su Telegram Per esempio nel caso a noi servisse l'id della persona che ha mandato il messaggio basterà aprire la documentazione delle APIs di Telegram (https://core.telegram.org/bots/api#update) e: 1) Andare a vedere update, in questo caso ci serve message 2) Andare a vedere message cliccando sul link, poi ci servirà from 3) Andare a vedere from e prendere c…
26 Jan 2018, 04:16 UTC925 viewsread 11 August 2026
Photo
Photo, posted without a caption
26 Jan 2018, 02:53 UTC803 viewsread 11 August 2026
Dopo aver fatto ciò il bot sarà installato e pronto all'uso, ora non vi resta da modificare il file commands.php per creare i vostri comandi
26 Jan 2018, 02:42 UTC766 viewsread 11 August 2026
Settaggio webhook tramite setup.php Saltate questo messaggio se avete settato il webhook manualmente 1) Aprire setup.php nel browser 2) Cliccare "Yes" se non sono state fatte particolari configurazioni al server o ai file, se invece il link risulta non essere corretto cliccare "No" e inserite il link a cui settare il webhook 3) Prendere il token da @BotFather e inserirlo nel form 4) Se al termine vedrete "Bot: @Nom…
26 Jan 2018, 02:38 UTC727 viewsread 11 August 2026
Installazione 1) Scaricare da https://github.com/davtur19/TuriBot i file di TuriBot 2) Copiare tutti i file in una cartella del proprio web server 3) Impostare il webhook, si può fare manualmente o utilizzando setup.php
26 Jan 2018, 02:28 UTC699 viewsread 11 August 2026
Benvenuto nella guida per creare un bot Telegram usando TuriBot Requisiti 1) Saper programmare in PHP 2) Un server web che supporti PHP e cURL 3) Il server web deve avere un certificato SSL valido 4) Il server web deve essere raggiungibile dai server di Telegram
26 Jan 2018, 02:24 UTCviews —
Channel created
Showing the 12 most recent of 12 posts we hold for @TuriBotGuida. 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.
Citation-graph rank
Citation-graph rank — 1,402,326 of 1,549,376entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@TuriBotGuida named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@nomedeltuobot
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“TuriBot Guida” (@TuriBotGuida), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TuriBotGuida.
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.