Этот вечер спасут они 🦸 Вместе с Романом Шубиным, CTO и автором канала Bash Days, собрали новую подборку консольных команд. Она облегчит жизнь системного администратора — сохраняйте! Кстати, это уже третий пост подборки. Еще больше команд — в первой и второй частях. Не забудьте поделиться находкой с коллегами!

Channel
Bash Days | Linux | DevOps
@bashdays
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
23,640subscribers
-120 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001869873447 |
|---|---|
| Type | Channel |
| Username | @bashdays |
| Description | Авторский блог от действующего девопса Самобытно про разработку, devops, linux, скрипты, сисадминство, техдирство и за айтишную жизу. Автор: Роман Шубин Реклама: @maxgrue MAX: https://max.ru/bashdays Курс: @tormozilla_bot Блог: https://bashdays.ru |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/bashdays |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 06:40 | 23,640 | +6 |
| 25 Sept 2026, 12:01 | 23,634 | -40 |
| 18 Sept 2026, 21:41 | 23,674 | +16 |
| 16 Sept 2026, 15:19 | 23,658 | -10 |
| 14 Sept 2026, 20:00 | 23,668 | -6 |
| 13 Sept 2026, 09:01 | 23,674 | +2 |
| 11 Sept 2026, 10:38 | 23,672 | -15 |
| 8 Sept 2026, 16:16 | 23,687 | -14 |
| 5 Sept 2026, 06:38 | 23,701 | -1 |
| 3 Sept 2026, 10:59 | 23,702 | -7 |
| 2 Sept 2026, 05:04 | 23,709 | -1 |
| 1 Sept 2026, 07:37 | 23,710 | -8 |
| 30 Aug 2026, 02:13 | 23,718 | -7 |
| 28 Aug 2026, 22:58 | 23,725 | -8 |
| 27 Aug 2026, 21:04 | 23,733 | -4 |
| 27 Aug 2026, 00:13 | 23,737 | -4 |
| 26 Aug 2026, 00:04 | 23,741 | -2 |
| 25 Aug 2026, 01:14 | 23,743 | +5 |
| 21 Aug 2026, 19:03 | 23,738 | -4 |
| 20 Aug 2026, 19:33 | 23,742 | first reading |
Engagement
36 posts held, back to 12 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 85 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 23.2%
- avg views ÷ 23,640 subscribers
- Avg views / post
- 5,470
- 11 posts measured
- Reaction rate
- 0.392%
- reactions ÷ views · ER floor
- Posts in window
- 11
- of 36 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 10 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 October 2026 |
|---|---|
| Posts held | 36 (12 July 2026 – 6 October 2026) |
| Views total | 60,220 |
| Reactions total | 236 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 13:39 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 230
- Videos
- 26
- Links
- 779
Lifetime counters from Telegram’s own channel header, read 6 October 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.
- Video runtime
- 15s
- Average length
- 15s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,431 reactions across 35 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5411157574571545064 | 1,431 | 100.0% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 35 of the 36 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,431 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 12 July 2026 to 6 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
- Stars received
- 18
- across the posts below
- Posts paid on
- 11
- of 36 we hold a reading for · 31%
- Most on one post
- 4
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bashdays. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 36 most recent posts we hold for this entry, published 12 July 2026 to 6 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
- Ad load
- 2.78%
- 1 of 36 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 6,550
- over 1 measured post
- Median views · rest
- 8,350
- over 35 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqwngdhU | 1 | 3 August 2026 | 3 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 36 most recent posts we hold, published 12 July 2026 to 6 October 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Linux, контейнеры и ИБ: без сказок, с демо 8 октября в 11:00 приходите на стрим «Лаборатории Касперского» про проактивную защиту контейнерных сред. Эксперты наглядно покажут Kaspersky Container Security, разберут актуальные угрозы для контейнеров, подискутируют о важности антивирусного движка и зайдут на поляну Managed Kubernetes. Ну и на вопросы зрителей в прямом эфире ответят. Регистрируйтесь
custom 54111575745715450642
Архивирование и хранение. Часть 2/4. Всем привет, с вами снова TagdTagd. Первая часть тут: https://t.me/bashdays/1561 Я уже упоминал программу par2. Она разрабатывалась очень давно, скорее всего во времена ленточных накопителей. И ее логика работы не совсем понятна современным пользователям. Блоки четности разбиваются на несколько файлов. Сделано это было по нескольким причинам: 1. par2 - старая программа, и там …
custom 541115757457154506422
↗️ Для всех, кто строит 15 октября Cloud․ru соберет инженеров, которые строят и эксплуатируют сложные платформы и отказоустойчивые сервисы. В программе: ▶️как перестроить сетевую архитектуру облака под 10 000 гипервизоров на зону доступности ▶️как добавить поддержку NVLink в облачную инфраструктуру ▶️как управлять InfiniBand и балансировать ИИ-кластер ▶️как перестроить DBaaS с помощью Kubernetes ▶️как создать с…
custom 54111575745715450644
Самый жаркий холивар в команде — это не systemd, а какие заказать роллы на всю команду. Одному без острого, другому без сыра, третьему лишь бы побольше. Полчаса споров, дружное почёсывание репы, и в итоге все заказывают пиццу. А тут прилетает: Ёёёёёёё с Yandex Cloud собирают набор для айтишников и спрашивают их, что туда класть. Вот это настоящий импрувмент. В опросе есть и размер, и когда вообще едят роллы, вплоть…
custom 541115757457154506417
Posted without readable text
custom 54111575745715450649
Здрасти приехали, решил я в кой-то веке воспользоваться услугами Codex, создал аккаунт, пополнил баланс через хуй-пизда-копыто и вот они финальные метры до финиша… Хуй там плавал. Эта залупа требует верификацию по номеру телефона, естественно РФ номера не подходят. Почесал я репу, поплакал, но нюни не стал распускать. Мыж инженеры, надо искать способы решить этот внезапный квест. Покупка одноразового номера не подх…
custom 541115757457154506472
Всем привет, с вами TagdTagd. Сегодня опять поднимем тему архивов, но немного с другой стороны. Поговорим о сохранности данных. Вот здесь https://t.me/bashdays/1402 уже немного касался этой проблемы, теперь немного расширим. Часть 1/4. Итак - архивы растут. Диски растут. А надежность при этом падает. Этож и ёжику резиновому понятно, что чем больше файл, тем больше вероятность получить дырочку в правом боку. Конечн…
custom 541115757457154506425
Всем привет, с вами TagdTagd. И это вторая часть. Практическая. С первой частью можешь ознакомиться здесь Скрипт писался с привлечением ИИ, но мной отлажен, и точно работает. Требует jq и curl. В отличие от телеграма, в максе заявлено, что бот может писать сообщения пользователю тольков течение суток, после последнего сообщения пользователя боту. Поэтому для нормальной работы оповещателя желательно создать группу,…
custom 541115757457154506425
Всем привет, с вами TagdTagd! Я тут вынужденно перешёл на MAX. Просто Telegram перестал работать хорошо. Пришлось разбираться с новым API, переделывать уведомления с Telegram на MAX. Решил вот с вами поделиться опытом — может, кому-то пригодится. За это время пришлось решить несколько проблем: 1. У MAX под Linux не работал звук. Была проблема с прослушиванием аудио/видео и звонками. 2. MAX постоянно допиливают, п…
custom 541115757457154506422
Напьются своих рафов лавандовых, а потом в жопы ебутся… На фоне переезда на линукс, я знатно упоролся и ушел в сторону разработки. На этот раз я решил закрыть свои гештальты, которые преследовали меня последние несколько лет. Короче сначала я запили плагин для Obsidian и даже удалось захуячить его в официальный стор плагинов самого обсидиана. Штуку я назвал Cursor Layout Indicator. Суть такая, что рядом с курсором…
custom 541115757457154506438
Kubernetes на минималках Поднимаем K3s локально и не ноем про инфраструктуру Кто хочет — ищет способ, кто не хочет — ищет причину. В четвёртом сезоне Linux Factory мы собираем нормальный отказоустойчивый кубер: три control-ноды, три worker-ноды, HAProxy, Keepalived, VIP, отдельный DNS и хранилище. Это правильно для обучения инфраструктуре, но даже в минимальной конфигурации получается шесть виртуалок по 2 CPU и 2…
custom 541115757457154506441
Showing the 12 most recent of 36 posts we hold for @bashdays. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 4 registered channels — 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@devopsina · 23,613#1
@srv_admin · 32,593#2
@admguides · 11,960#3
@usr_bin_linux · 4,922#4
@devops_memops · 6,340#5
@linux_gram · 13,704#6
@devops_fm · 5,282#7
@Social_engineering · 124,999#8
@rebrain_devops · 28,853#9
@devopsslib · 10,371#10
@devops_interview_lib · 3,460#11
@DevOPSitsec · 23,671#12
@sysodmins_league · 13,279#13
@ITKB_channel · 7,997#14
@pylinux0 · 11,043#15
@count0_digest · 4,760#16
@linux_sup · 7,429#17
@i_DevOps · 8,820#18
@interface31 · 8,993#19
@sysadmin_library · 25,522#20
@os_linux_ru · 19,602#21
@school_network · 26,560#22
@sysodmins · 38,258#23
@linuxkalii · 55,481#24
@linuxacademiya · 28,459#25
@devops_problems_lib · 3,013#26
@i_odmin · 26,681#27
@devops_factory · 1,723#28
@DOFH_ru · 3,792#29
@bezopasno_soft · 29,634#30
@iscode · 5,787#31
@devops_sc · 14,824#32
@DevOpsKaz · 6,867#33
@cybersec_academy · 42,827#34
@deusops · 3,086#35
@IT_Portal · 99,777#36
@dev_ops_info · 2,188#37
@linuxcamp_tg · 13,582#38
@etogeek · 4,382#39
@gitgate · 6,780#40
@monitorim_it · 8,534#41
@SysadminNotes · 12,741#42
@easy_devops · 5,574#43
@devopsgarden · 4,397#44
@it_secur · 62,254#45
@devopslibrary · 19,877#46
@k8security · 13,185#47
@linkmeup_podcast · 17,446#48
@theaftertimes · 16,820#49
@tech_b0lt_Genona · 9,797#50
@open_source_friend · 52,333#51
@opennet_ru · 15,777#52
@devsecops_weekly · 8,042#53
@worlditech · 7,275#54
@habr_com · 132,847#55
@devops_jobs_feed · 21,994#56
@devopsupgrade · 5,321#57
@devops_deflope · 5,838#58
@bykvaadm · 6,429#59
@rozetked · 666,897#60
@itmemes · 122,995#61
@tg_infosec · 26,761#62
@ittales · 1,690#63
@whackdoor · 1,586,239#64
@SecLabNews · 84,790#65
@github · 155,595#66
@recura_tech · 14,622 (as read 18 September 2026)#67
@S_E_Reborn · 22,399#68
@true_secator · 41,782#69
@zatelecom · 64,306#70
@Selectel · 63,091#71
@mikrotik_sensei · 19,556#72
@network_quiz · 7,254#73
@zabbix_ru · 3,629#74
@slurmnews · 8,065#75
@S_E_Book · 23,139#76
@opengrad · 748#77
@mikrotikninja · 3,981#78
@localhost_public · 16,739#79
@easy_devops_tests · 2,672#80
@black_triangle_tg · 63,815#81
@devopssjob · 4,483#82
@Golang_google · 40,420#83
@kubertat · 506#84
@networkadminru · 4,704#85
@nsis_cybersec · 21,516#86
@dvachannel · 942,201#87
@networkadm · 12,361#88
@exploitex · 2,048,192#89
@k8sjust · 1,077#90
@net_arch · 7,428#91
@addmeto · 71,819#92
@dataleak · 118,872#93
@oper_goblin · 492,891#94
Read from Telegram’s recommendation API, most recently 18 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@os_linux_ru · 19,602
Telegram ranks this channel #2 of 87 here — alongside 86 others — read 1 October 2026
@devopsina · 23,613
Telegram ranks this channel #2 of 90 here — alongside 89 others — read 18 September 2026
@rebrain_devops · 28,853
Telegram ranks this channel #2 of 94 here — alongside 93 others — read 9 September 2026
@srv_admin · 32,593
Telegram ranks this channel #2 of 96 here — alongside 95 others — read 5 September 2026
@sysadmin_library · 25,522
Telegram ranks this channel #8 of 85 here — alongside 84 others — read 13 September 2026
@DevOPSitsec · 23,671
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 18 September 2026
@school_network · 26,560
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 12 September 2026
@linuxacademiya · 28,459
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 9 September 2026
@i_odmin_book · 18,737
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 5 October 2026
@linuxkalii · 55,481
Telegram ranks this channel #16 of 89 here — alongside 88 others — read 23 August 2026
@i_odmin · 26,681
Telegram ranks this channel #17 of 89 here — alongside 88 others — read 12 September 2026
@devops_jobs_feed · 21,994
Telegram ranks this channel #19 of 95 here — alongside 94 others — read 22 September 2026
@sysodmins · 38,258
Telegram ranks this channel #23 of 93 here — alongside 92 others — read 31 August 2026
@mikrotik_sensei · 19,556
Telegram ranks this channel #24 of 92 here — alongside 91 others — read 1 October 2026
@devopsforlove · 44,635
Telegram ranks this channel #28 of 95 here — alongside 94 others — read 9 September 2026
@cybersec_academy · 42,827
Telegram ranks this channel #30 of 70 here — alongside 69 others — read 29 August 2026
@itdoginfo · 19,313
Telegram ranks this channel #33 of 87 here — alongside 86 others — read 2 October 2026
@bezopasno_soft · 29,634
Telegram ranks this channel #34 of 78 here — alongside 77 others — read 8 September 2026
@open_source_friend · 52,333
Telegram ranks this channel #43 of 87 here — alongside 86 others — read 24 August 2026
@EnglishScript · 44,988
Telegram ranks this channel #46 of 82 here — alongside 81 others — read 27 August 2026
@Selectel · 63,091
Telegram ranks this channel #48 of 96 here — alongside 95 others — read 21 August 2026
@devopslibrary · 19,877
Telegram ranks this channel #50 of 94 here — alongside 93 others — read 30 September 2026
@book_academ · 21,410
Telegram ranks this channel #53 of 72 here — alongside 71 others — read 23 September 2026
@Social_engineering · 124,999
Telegram ranks this channel #53 of 82 here — alongside 81 others — read 13 August 2026
This channel appears in 39 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Bash Days | Linux | DevOps” (@bashdays), 23,640 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/bashdays.
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.