Telegram RegisterThe public register of Telegram
Telegram profile photo for 📁 Teams Database

Channel

📁 Teams Database

@YSC_TEAMS_DATABASE

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

27subscribers

-1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004388800960
TypeChannel
Username@YSC_TEAMS_DATABASE
CreatedBetween 1 June 2026 and 20 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live30 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 30 August 2026
On Telegramt.me/YSC_TEAMS_DATABASE

Growth

272827.59 August 2026 — 28 subscribers11 August 2026 — 28 subscribers16 August 2026 — 27 subscribers9 August 202616 August 2026
3 measurements spanning 8 days, net -1. 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 27–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 16:0827-1
11 Aug 2026, 06:4528no change
9 Aug 2026, 03:0328first reading

Engagement

20 posts held, back to 20 June 2026the 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 20 posts for this entry, the most recent from 2 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jul 2026, 12:49 UTC95 viewsread 11 August 2026
Photo

#UTT000T25 || Lᴜᴄᴋʏ ʟᴇɢᴇɴᴅs ① Jᴜɴ 22 • 𝟾:𝟹𝟶 PM 🆚 Bʟᴀᴄᴋ Kɴɪɢʜᴛs BK : 9 Cᴀʀᴅs | 124 Pᴛs LL : 0 Cᴀʀᴅs | 2 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜʟ 𝟶𝟹 • 𝟾:𝟶𝟶 PM 🆚 Cᴏᴄᴋʀᴏᴀᴄʜ Wᴀʀʀɪᴇʀs LL : 102 Cᴀʀᴅs | 12 Pᴛs CW : 0 Cᴀʀᴅs | 2 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟾 • 𝟾:𝟹𝟶 PM 🆚 Uɴᴏ Wᴀʀʀɪᴏʀs LL : 12 Cᴀʀᴅs | 141 Pᴛs UW : 0 Cᴀʀᴅs | 14 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟷 • 𝟾:𝟶𝟶 PM 🆚 Uɴᴏ ᴩᴏᴡᴇʀʜᴏᴜꜱᴇ LL : 6 Cᴀʀᴅs | 32 P

20 Jun 2026, 17:16 UTC131 viewsread 11 August 2026
Photo

🏷️ #UTT000T24 | Tᴀᴍɪʟ Rᴏᴄᴋᴇʀs ① Jᴜɴ 𝟸𝟷 • 𝟿:𝟶𝟶 PM 🆚 Mᴀɢɪᴄ Mᴇᴍᴏʀɪᴇs TR : 2 Cᴀʀᴅs | 6 Pᴛs MM : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟻 • 𝟾:𝟶𝟶 PM 🆚 Cᴏᴄᴋʀᴏᴀᴄʜ Wᴀʀʀɪᴇʀs TR : 5 Cᴀʀᴅs | 41 Pᴛs CW : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟿 • 𝟾:𝟶𝟶 PM 🆚 Rᴀᴀᴛʜɪʀɪ Rᴀᴀᴊᴀɴɢᴀᴍ TR : 0 Cᴀʀᴅs | 16 Pᴛs RR : 13 Cᴀʀᴅs | 68 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟽 • 𝟿:𝟶𝟶 PM 🆚 Nᴀᴍᴍᴀ Aʀᴇᴀ TR : 0 Cᴀʀᴅs | 0 Pᴛs NA

20 Jun 2026, 17:15 UTC81 viewsread 11 August 2026
Photo

🏷️ #UTT000T23 | Tᴀᴍɪʟ Asɪᴀ ① Jᴜɴ 𝟷𝟿 • 𝟿:𝟶𝟶 PM 🆚 Lᴜᴄᴋʏ Dʀᴇᴀᴍᴇʀ TA : 0 Cᴀʀᴅs | 0 Pᴛs LD : 10 Cᴀʀᴅs | 112 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜʟ 𝟶𝟸 • 𝟾:𝟹𝟶 PM 🆚 Tᴇᴀᴍ ᴏғ Cʀɪᴍɪɴᴀʟ TA : 32 Cᴀʀᴅs | 293 Pᴛs TOC : 10 Cᴀʀᴅs | 85 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟻 • 𝟿:𝟶𝟶 PM 🆚 Nᴇᴇʟᴀᴍʙᴀʀɪ Sǫᴜᴀᴅ TA : 7 Cᴀʀᴅs | 30 Pᴛs NS : 0 Cᴀʀᴅs | 4 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟻 • 𝟿:𝟶𝟶 PM 🆚 Tᴇᴀᴍ Cᴏɴɴᴇᴄᴛɪᴏɴ TA : 0 Cᴀʀᴅs | 0 Pᴛs

20 Jun 2026, 17:15 UTC66 viewsread 11 August 2026
Photo

🏷️ #UTT000T22 | Nᴀᴍᴍᴀ Aʀᴇᴀ ① Jᴜɴ 𝟷𝟻 • 𝟾:𝟶𝟶 PM 🆚 Aᴅᴇɴɢᴀᴘᴘᴀ 𝟺 Pᴇʀᴜ NA : 0 Cᴀʀᴅs | 12 Pᴛs A𝟺P : 3 Cᴀʀᴅs | 58 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟹 • 𝟾:𝟶𝟶 PM 🆚 Pᴜʟʟɪ Mᴀᴀɴɢᴀʟ NA : 0 Cᴀʀᴅs | 0 Pᴛs PM : 3 Cᴀʀᴅs | 11 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜɴ 𝟸𝟻 • 𝟿:𝟶𝟶 PM 🆚 Lᴜᴄᴋʏ Dʀᴇᴀᴍᴇʀ NA : 14 Cᴀʀᴅs | 109 Pᴛs LD : 8 Cᴀʀᴅs | 68 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟶𝟼 • 𝟾:𝟹𝟶 PM 🆚 Uɴᴏ ᴩᴏᴡᴇʀʜᴏᴜꜱᴇ NA : 0 Cᴀʀᴅs | 0 Pᴛs UP :

20 Jun 2026, 17:15 UTC59 viewsread 11 August 2026
Photo

🏷️ #UTT000T21 | Rᴏʏᴀʟ ᴄʜᴀʟʟᴇɴɢᴇʀs Bᴀɴɢᴀʟᴏʀᴇ ① Jᴜɴ 𝟸𝟶 • 𝟾:𝟹𝟶 PM 🆚 Tᴇᴀᴍ Bᴇᴛᴀ RCB : 1 Cᴀʀᴅs | 6 Pᴛs TB : 0 Cᴀʀᴅs | 10 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜʟ 𝟶𝟽 • 𝟾:𝟶𝟶 PM 🆚 Lᴀsᴛ Bᴇɴᴄʜ 𝟺 Pᴇʀᴜ RCB : 0 Cᴀʀᴅs | 10 Pᴛs LB𝟺 : 2 Cᴀʀᴅs | 15 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟷𝟺 • 𝟾:𝟹𝟶 PM 🆚 Pᴜʟʟɪ Mᴀᴀɴɢᴀʟ RCB : 0 Cᴀʀᴅs | 0 Pᴛs PM : 9 Cᴀʀᴅs | 60 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟻 • 𝟾:𝟶𝟶 PM 🆚 Bʀᴀᴢɪʟ RCB : 0 Cᴀʀᴅs | 0 Pᴛ

20 Jun 2026, 17:13 UTC52 viewsread 11 August 2026
Photo

🏷️ #UTT000T19 | Tᴇᴀᴍ 𝟷𝟷 Cʀᴇᴡ ① Jᴜɴ 𝟷𝟽 • 𝟿:𝟶𝟶 PM 🆚 Bᴀʀᴄᴇʟᴏɴᴀ T𝟷𝟷 : 10 Cᴀʀᴅs | 83 Pᴛs BAR : 0 Cᴀʀᴅs | 6 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜʟ 𝟶𝟷 • 𝟾:𝟶𝟶 PM 🆚 Bʟᴀᴄᴋ Kɴɪɢʜᴛs T𝟷𝟷 : 22 Cᴀʀᴅs | 189 Pᴛs BK : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟽 • 𝟿:𝟶𝟶 PM 🆚 Mᴀɢɪᴄ Mᴇᴍᴏʀɪᴇs T𝟷𝟷 : 0 Cᴀʀᴅs | 0 Pᴛs MM : 16 Cᴀʀᴅs | 81 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟿 • 𝟿:𝟶𝟶 PM 🆚 Aᴅᴇɴɢᴀᴘᴘᴀ 𝟺 Pᴇʀᴜ T𝟷𝟷 : 0 Cᴀʀᴅs | 0 Pᴛs A𝟺P

20 Jun 2026, 17:13 UTC54 viewsread 11 August 2026
Photo

🏷️ #UTT000T20 | Tᴇᴀᴍ ᴏғ Cʀɪᴍɪɴᴀʟ ① Jᴜɴ 𝟷7 • 𝟾:𝟹𝟶 PM 🆚 Iɴᴅɪᴀ ᴠs Pᴀᴋɪsᴛᴀɴ TOC : 17 Cᴀʀᴅs | 121 Pᴛs IVP : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜʟ 𝟶𝟷 • 𝟿:𝟶𝟶 PM 🆚 Team connection TOC : 14 Cᴀʀᴅs | 175 Pᴛs CW : 0 Cᴀʀᴅs | 2 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟸 • 𝟾:𝟹𝟶 PM 🆚 Tᴀᴍɪʟ Asɪᴀ TOC : 10 Cᴀʀᴅs | 85 Pᴛs TA : 32 Cᴀʀᴅs | 293 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟶𝟺 • 𝟾:𝟹𝟶 PM 🆚 Bʟᴀᴄᴋ Kɴɪɢʜᴛs TOC : 9 Cᴀʀᴅs

20 Jun 2026, 17:13 UTC76 viewsread 11 August 2026
Photo

🏷️ #UTT000T18 | Lᴀsᴛ Bᴇɴᴄʜ 𝟺 Pᴇʀᴜ ① Jᴜɴ 𝟸𝟷 • 𝟾:𝟶𝟶 PM 🆚 Rᴀᴀᴛʜɪʀɪ Rᴀᴀᴊᴀɴɢᴀᴍ LB𝟺 : 3 Cᴀʀᴅs | 10 Pᴛs RR : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟹 • 𝟿:𝟶𝟶 PM 🆚 Bᴀʀᴄᴇʟᴏɴᴀ LB𝟺 : 0 Cᴀʀᴅs | 10 Pᴛs BAR : 4 Cᴀʀᴅs | 32 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟹 • 𝟿:𝟶𝟶 PM 🆚 Mᴀɢɪᴄ Mᴇᴍᴏʀɪᴇs LB𝟺 : 18 Cᴀʀᴅs | 146 Pᴛs MM : 13 Cᴀʀᴅs | 124 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟶𝟽 • 𝟾:𝟶𝟶 PM 🆚 Rᴏʏᴀʟ ᴄʜᴀʟʟᴇɴɢᴇʀs Bᴀɴɢᴀʟᴏʀᴇ LB

20 Jun 2026, 17:13 UTC64 viewsread 11 August 2026
Photo

🏷️ #UTT000T17 | Uɴᴏ Wᴀʀʀɪᴏʀs ① Jᴜɴ 𝟸𝟿 • 𝟾:𝟶𝟶 PM 🆚 Sᴄᴀʀʟᴇᴛ Wɪɴɢs UW : 4 Cᴀʀᴅs | 37 Pᴛs SW : 40 Cᴀʀᴅs | 216 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟹𝟶 • 𝟾:𝟹𝟶 PM 🆚 Bʟᴀᴄᴋ Kɴɪɢʜᴛs UW : 4 Cᴀʀᴅs | 42 Pᴛs BK : 2 Cᴀʀᴅs | 31 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟻 • 𝟾:𝟶𝟶 PM 🆚 Rᴀᴀᴛʜɪʀɪ Rᴀᴀᴊᴀɴɢᴀᴍ UW : 0 Cᴀʀᴅs | 0 Pᴛs RR : 171 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟶𝟾 • 𝟾:𝟹𝟶 PM 🆚 Lᴜᴄᴋʏ ʟᴇɢᴇɴᴅs UW : 0 Cᴀʀᴅs | 14 Pᴛs

20 Jun 2026, 17:12 UTC69 viewsread 11 August 2026
Photo

🏷️ #UTT000T16 | Nᴇᴇʟᴀᴍʙᴀʀɪ Sǫᴜᴀᴅ ① Jᴜɴ 𝟷𝟻 • 𝟾:𝟹𝟶 PM 🆚 Cᴏᴄᴋʀᴏᴀᴄʜ Wᴀʀʀɪᴏʀs NS : 10 Cᴀʀᴅs | 76 Pᴛs CW : 8 Cᴀʀᴅs | 79 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟿 • 𝟿:𝟶𝟶 PM 🆚 Rᴀᴀᴛʜɪʀɪ Rᴀᴀᴊᴀɴɢᴀᴍ NS : 8 Cᴀʀᴅs | 109 Pᴛs RR : 8 Cᴀʀᴅs | 25 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜʟ 𝟶𝟻 • 𝟿:𝟶𝟶 PM 🆚 Tᴀᴍɪʟ Asɪᴀ NS : 0 Cᴀʀᴅs | 4 Pᴛs TA : 7 Cᴀʀᴅs | 30 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟸 • 𝟾:𝟹𝟶 PM 🆚 Uɴᴏ ᴩᴏᴡᴇʀʜᴏᴜꜱᴇ NS : 0 Cᴀʀᴅs | 4

20 Jun 2026, 17:09 UTC81 viewsread 11 August 2026
Photo

🏷️ #UTT000T15 | Sᴄᴀʀʟᴇᴛ Wɪɴɢs ① Jᴜɴ 𝟷𝟼 • 𝟾:𝟹𝟶 PM 🆚 Tᴇᴀᴍ Cᴏɴɴᴇᴄᴛɪᴏɴ SW : 6 Cᴀʀᴅs | 59 Pᴛs TC : 1 Cᴀʀᴅs | 24 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟼 • 𝟾:𝟹𝟶 PM 🆚 Wʜɪᴛᴇ Mᴏᴏɴ SW : 40 Cᴀʀᴅs | 216 Pᴛs WM : 40 Cᴀʀᴅs | 216 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜɴ 𝟸𝟿 • 𝟾:𝟶𝟶 PM 🆚 Uɴᴏ Wᴀʀʀɪᴏʀs SW : 40 Cᴀʀᴅs | 216 Pᴛs UW : 4 Cᴀʀᴅs | 37 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟷 • 𝟾:𝟶𝟶 PM 🆚 Wʜɪᴛᴇ Mᴏᴏɴ SW : 40 Cᴀʀᴅs | 216 Pᴛs WM :

20 Jun 2026, 17:09 UTC80 viewsread 11 August 2026
Photo

🏷️ #UTT000T14 | Pᴜʟʟɪ Mᴀᴀɴɢᴀʟ ① Jᴜɴ 𝟷𝟾 • 𝟾:𝟹𝟶 PM 🆚 Wʜɪᴛᴇ Mᴏᴏɴ PM : 0 Cᴀʀᴅs | 4 Pᴛs WM : 40 Cᴀʀᴅs | 216 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ② Jᴜɴ 𝟸𝟹 • 𝟾:𝟶𝟶 PM 🆚 Nᴀᴍᴍᴀ Aʀᴇᴀ PM : 3 Cᴀʀᴅs | 11 Pᴛs NA : 0 Cᴀʀᴅs | 0 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ③ Jᴜɴ 𝟸𝟽 • 𝟿:𝟶𝟶 PM 🆚 Mᴀɢɪᴄ Mᴇᴍᴏʀɪᴇs PM : 12 Cᴀʀᴅs | 105 Pᴛs MM : 0 Cᴀʀᴅs | 2 Pᴛs 📊 Sᴄᴏʀᴇ Bᴏᴀʀᴅ ━━━━━━━━━━ ④ Jᴜʟ 𝟷𝟺 • 𝟾:𝟹𝟶 PM 🆚 Rᴏʏᴀʟ ᴄʜᴀʟʟᴇɴɢᴇʀs Bᴀɴɢᴀʟᴏʀᴇ PM : 9 Cᴀʀᴅs | 60

Showing the 12 most recent of 20 posts we hold for @YSC_TEAMS_DATABASE. 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,186,427 of 1,626,935entries 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.

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

“📁 Teams Database” (@YSC_TEAMS_DATABASE), 27 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/YSC_TEAMS_DATABASE.

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.