Telegram RegisterThe public register of Telegram
Telegram profile photo for AndrOBD

Channel

AndrOBD

@AndrOBD_dev

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

417subscribers

+18 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-1001352513492
TypeChannel
Username@AndrOBD_dev
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/AndrOBD_dev

Topic

Technology — 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 97% 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

3994174087 August 2026 — 399 subscribers8 August 2026 — 399 subscribers15 August 2026 — 402 subscribers24 August 2026 — 403 subscribers30 August 2026 — 401 subscribers15 September 2026 — 403 subscribers29 September 2026 — 410 subscribers9 October 2026 — 417 subscribers7 August 20269 October 2026
8 measurements spanning 63 days, net +18. 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 396–420 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 17:16417+7
29 Sept 2026, 21:16410+7
15 Sept 2026, 10:16403+2
30 Aug 2026, 15:05401-2
24 Aug 2026, 00:16403+1
15 Aug 2026, 12:34402+3
8 Aug 2026, 05:49399no change
7 Aug 2026, 20:12399first reading

Engagement

20 posts held, back to 1 April 2024 — 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 6 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Jul 2026, 06:33 UTC212 viewsread 8 August 2026

A new release is on it's way: https://github.com/fr3ts0n/AndrOBD/releases/tag/V2.7.10 It will be available on F-Droid soon. Thanks to @chrisdebian for all his inputs, fixes and perfectly prepared PR's! 👍

12 May 2026, 05:29 UTC420 viewsread 8 August 2026

Started a release of AndrOBD V2.7.9 https://github.com/fr3ts0n/AndrOBD/releases/tag/V2.7.9 Will be available on FDroid soon. 🚀

28 Apr 2026, 06:46 UTC523 viewsread 8 August 2026

A new BETA V2.7.8 is available at GitHub for testing https://github.com/fr3ts0n/AndrOBD/actions/runs/24996458945/artifacts/6661196590 - Fixed permission requests for Android versions <=5 - removed hidden logic for DEMO selection - DEMO is now a OBD adapter type - Default for new instalations - Selectable in Settings - Fixed theming at app startup - Allow AndrOBD to open .obd files

28 Mar 2026, 13:15 UTC534 viewsread 8 August 2026

Started a new release with (V2.7.6) with full Android 16 support. Builds are running. Should be available on F-Droid soon. 🚀

17 Mar 2026, 15:59 UTC582 viewsread 8 August 2026

I reworked the code to target Android SDK 36, so there is NO complaint about "old" app any more. - PopUp for "nearby devices" now gets visible/selectable - after allowing nearby devices, it will start fine ... - Initial run still may end in a failure, since permission dialog is asynchronous. I created a Beta (V2.7.5) to verify the fix: https://github.com/fr3ts0n/AndrOBD/actions/runs/23202720617/artifacts/5967987149

27 Feb 2026, 19:04 UTC613 viewsread 8 August 2026

Again a BETA update with BLE (V2.7.3): https://github.com/fr3ts0n/AndrOBD/actions/runs/22499641604/artifacts/5695688645 Changes: - Still fixing Permission glitches throughout different Android versions 😢

24 Feb 2026, 15:11 UTC579 viewsread 8 August 2026

Another updated BETA with BLE: https://github.com/fr3ts0n/AndrOBD/actions/runs/22356685423/artifacts/5637108536 Changes: Fix BT/BLE permissions - inclusive COARSE/FINE location

22 Feb 2026, 11:48 UTC519 viewsread 8 August 2026

Updated BETA version (V2.7.2) with BLE: https://github.com/fr3ts0n/AndrOBD/actions/runs/22276446976/artifacts/5606767689 Changes: - Hopefully final fixes of BT/BLE permissions 😉

22 Feb 2026, 10:07 UTC431 viewsread 8 August 2026

Updated BETA version for BLE testing: https://github.com/fr3ts0n/AndrOBD/actions/runs/22274917533/artifacts/5606363255 Changes: - Fixed BT/BLE permission checks throough various Android variants

22 Feb 2026, 07:03 UTC386 viewsread 8 August 2026

Updated BETA version with BLE: https://github.com/fr3ts0n/AndrOBD/actions/runs/22272242244/artifacts/5605628034 Changes: - Fixed logging to contain all relevant BLE info in *fine* level

20 Feb 2026, 08:26 UTC383 viewsread 8 August 2026

AndrOBD now does BLE 👍 Beta version (V2.7.0) with BLE support is here: https://github.com/fr3ts0n/AndrOBD/actions/runs/22216484272/artifacts/5586219788 I've tested with 2 BLE adapters so far: - VGate iCar Pro - Nexas NexLink Please test with your BLE adapters and confirm operation, or report with (fine) logfiles to issue https://github.com/fr3ts0n/AndrOBD/issues/241 Thx

Showing the 12 most recent of 20 posts we hold for @AndrOBD_dev. 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 9 October 2026 — this entry's latest reading, not the date you are reading this.

“AndrOBD” (@AndrOBD_dev), 417 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/AndrOBD_dev.

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.