#求职 Cindy @Cindy_zcz #只看远程 🌎 猎头对接:✅ 求职意向: #交易所 #运营 #数据 #项目管理 web3经验: 2-4年 工作经历: 曾担任多家头部中心化交易所的海外渠道运营,负责公司海外市场的合约活动,具备丰富的活动策划&数据分析经验,曾主导策划平台的大型交易赛活动。曾在全球领先的咨询公司担任咨询顾问,专注于金融科技&AI行业 擅长: 日常BD维护、活动运营与策划、 数据分析、制定并落地差异化运营&活动方案、驱动用户增长与转化 教育背景: 英国杜伦大学 毕业时间: 2016 学位: 硕士/研究生 专业: 金融 语言: #English #中文 待遇期待: 2500-3000u 合作心态: 随时合作

Channel
abetterpath 招聘求职
@abetterpathxyz
On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
33,176subscribers
-186 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001572924402 |
|---|---|
| Type | Channel |
| Username | @abetterpathxyz |
| Description | 机会聚合,人才流动。 专注全球华人职场交流与职业成长。 发布信息 -> https://t.me/abetterpathxyz/3977 筛选招聘 -> @abwfilterbot 只看招聘 -> @abetterpathjobs 只看人才 -> @abetterpathtalents 疑问/商务 @antoniayly Telegram广告切勿轻信,非频道自主推送。 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/abetterpathxyz |
Topic
Job listings — 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 9 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 why it has no browse page of its own yet.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 15:38 | 33,176 | -2 |
| 17 Sept 2026, 04:17 | 33,178 | -3 |
| 15 Sept 2026, 07:18 | 33,181 | +3 |
| 13 Sept 2026, 18:59 | 33,178 | -28 |
| 11 Sept 2026, 23:36 | 33,206 | -24 |
| 9 Sept 2026, 16:17 | 33,230 | -1 |
| 6 Sept 2026, 08:00 | 33,231 | -25 |
| 3 Sept 2026, 23:16 | 33,256 | +1 |
| 2 Sept 2026, 16:29 | 33,255 | +11 |
| 1 Sept 2026, 15:06 | 33,244 | -1 |
| 31 Aug 2026, 12:14 | 33,245 | +7 |
| 30 Aug 2026, 09:14 | 33,238 | -2 |
| 29 Aug 2026, 12:45 | 33,240 | -8 |
| 28 Aug 2026, 11:25 | 33,248 | -2 |
| 27 Aug 2026, 11:54 | 33,250 | +1 |
| 26 Aug 2026, 13:34 | 33,249 | -13 |
| 25 Aug 2026, 10:02 | 33,262 | -5 |
| 24 Aug 2026, 09:07 | 33,267 | -6 |
| 22 Aug 2026, 14:34 | 33,273 | -6 |
| 21 Aug 2026, 05:47 | 33,279 | first reading |
Engagement
309 posts held, back to 4 August 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 79 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.38%
- avg views ÷ 33,176 subscribers
- Avg views / post
- 1,120
- 140 posts measured
- Reaction rate
- 0.074%
- reactions ÷ views · ER floor
- Posts in window
- 140
- of 309 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 48 of 140 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 September 2026 |
|---|---|
| Posts held | 309 (4 August 2026 – 24 September 2026) |
| Views total | 156,852 |
| Reactions total | 45 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 18:37 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
- ≈704
- Videos
- ≈62
- Links
- ≈9,960
Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
116 reactions across 69 posts, in 8 distinct kinds. The most used accounts for 70.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 82 | 70.7% | |
| 👍 | 22 | 19.0% | |
| 🎉 | 5 | 4.31% | |
| 🔥 | 2 | 1.72% | |
| 🤔 | 2 | 1.72% | |
| ❤🔥 | 1 | 0.862% | |
| 🤣 | 1 | 0.862% | |
| 🤷 | 1 | 0.862% |
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 102 of the 309 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 309 most recent posts we hold, published 4 August 2026 to 24 September 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.
Recent posts
#求职 kuku @kukuzyy #全职 #兼职 #实习 #只看远程 🌎 猎头对接:✅ 求职意向: #运营 web3经验: 1-2年 工作经历: 2024.03-2024.10 Seamoon Protocol 社媒运营,负责Twitter/Telegram发文、活动策划及数据监测 2026.04-2026.06 TreeHub Web3社区运营,负责社群维护、内容选题、空投及研报分享 Noos Network 社群运营(Telegram日常巡群、内容转化、海报物料) 擅长: 擅长 社媒运营:X/Telegram/抖音内容策划、公告撰写与发布 社群运营:Telegram巡群、话题引导、用户答疑、氛围维护(交互量破万) Web3:DeFi/Meme/空投/Token Launch,链上数据观察(DexScreener/GeckoTerminal) Noos Network:AI Agent/Web3叙事内容转化、公告解读…
#招聘 https://x.com/haze0x/status/2102976871571009965
❤1
#求职 Eason @onlydevguy #只看远程 🌎 猎头对接:✅ 求职意向: #运维 web3经验: 1-2年 工作经历: 10年互联网后端与生产环境运维经验,负责支付、数字资产及高并发系统的部署发布与稳定性建设。 基于Linux/Docker/K8s管理多套生产环境,支持Go服务与Cocos Creator Web/Native构建产物发布,优化Nginx、HTTPS及CDN静态资源交付。 主导Jenkins/GitLab CI流水线建设,规范代码构建、灰度发布与快速回滚;编写Shell/Python脚本实现巡检、日志清理与数据校验自动化。 搭建Prometheus+Grafana+ELK/Loki监控体系,从服务器资源、JVM、MySQL慢查询及MQ积压多维度快速定位并解决线上故障。 完善安全策略,包括WAF、IP白名单、签名验签、DDoS防护基础及敏感日志脱敏,保障核心业务连续稳定。 擅长: 精通Linux(…
#求职 Jade @trondevy #只看远程 🌎 求职意向: #Go #PHP web3经验: < 1年 工作经历: 11年PHP/Go后端经验,主导核心业务系统(支付、订单、IM)的架构与开发。 设计多币种钱包、充值提现与清结算系统,通过账务分录、幂等键、分布式锁与对账补偿,保障资金最终一致性。 负责OpenIM私有化部署与源码二次开发,集成Laravel业务系统,实现WebSocket长连接、消息漫游、离线推送及多端同步。 使用Go/Gin开发高并发资金流水聚合与异步对账服务,结合pprof与压测优化CPU、内存及协程并发。 优化MySQL慢SQL与分库分表,利用Redis/Kafka/RabbitMQ解耦高并发链路,落地Docker/K8s及GitLab CI/CD自动化部署。 擅长: PHP/Laravel: 精通PHP7/8、Laravel8-11、Hyperf、Swoole;熟悉Eloquent、Horiz…
#求职 kevin [email protected] #全职 #只看远程 🌎 猎头对接:✅ 求职意向: #运营 web3经验: > 4年 工作经历: 深圳富途网络科技有限公司-财经内容运营 内容运营:热点快讯的生产,港美股盘面异动和热门资讯的推送,合作内容源的转载和个股运营 选题策划:金融市场和外媒热点的捕捉和筛选,和竞品对比,输出有流量转化效应、有价值和前瞻性的文章 擅长: 作能力:5年+从业经历,0-1完成多个项目孵化到指标稳定增长,掌握创作者运营、内容运营、活动策划 全生命周期,具备产品运营管理经验,精准定位产品功能优势亮点,擅长用户需求与痛点的产品化,擅长沟 通协调、资源整合 个人优势:主流内容社区产品5年以上的深度用户和博主,0-1主导产出千万级内容,出色的文字表达能 力,对热点话题与优质内容有较高敏感度,熟悉市场参与者的心理和偏好;对数据敏感,擅长进行数据处理 与分析、实现数据可视化 综合素养:多…
#求职 Ryan TG:web3opps7 #全职 #兼职 #只看远程 🌎 求职意向: #HRBP web3经验: 2-4年 工作经历: 10年乙方(Team Lead 专注传统金融 web3 高科技行业招聘)+ 1.5 年CEX 初创所 TA Leader(产研+非产研都负责,负责职位 海外BD 运营 市场 增长 产研等) 擅长: 中英流利,招聘:海外BD(CIS,LATAM,Africa,MENA,SEA,华语,英语等主要市场),市场,运营,增长 以及产研和职能岗 学位: 学士/本科 语言: #English #中文 待遇期待: 4500-5500u 可谈 合作心态: 随时合作
#求职 Max @chensilencer #全职 #兼职 #只看远程 🌎 猎头对接:✅ 求职意向: #开发 #交易所 web3经验: > 4年 工作经历: android负责人、flutter高级开发 擅长: 十年安卓开发、五年flutter经验 教育背景: 本科 毕业时间: 2014 学位: 学士/本科 专业: 计算机科学与技术 语言: #中文 #English 待遇期待: 面议 合作心态: 随时合作 更多链接: https://blog.csdn.net/u013095264?spm=1000.2115.3001.5343
#求职 飞机头 [email protected] #全职 #只看远程 🌎 猎头对接:✅ 求职意向: #全栈 #后端 #开发 #Go #Java #Solana #EVM #TypeScript 工作经历: Gate(2025.10–2026.04)|研发工程师:负责 Web3 交易/钱包业务与 Agent 项目,涉及多链资产交换、跨链消息通信、智能合约互操作,以及 Web3 交易接入 Gate AI 的工程落地。 Weex 唯客(2026.05–2026.09)|Agent 研发工程师:主导基于 Multica 的 AI Agent 工程化落地,构建面向交易业务与研发交付场景的 Multi-Agent 协作系统。 Go 项目经验:熟练使用 Go 进行后端服务开发,掌握 Goroutine、Channel、GMP 调度模型、内存逃逸分析与 GC 机制;有基于 Gin、Gorm 构建高并发接口、微服务调用链追踪、Kafka …
#求职 Brad @ivorywhitesnow #只看远程 🌎 求职意向: #后端 工作经历: 高并发与微服务: 主导单体系统向微服务架构演进,落地TCC分布式事务与幂等设计,解决高并发扣费超发;优化深分页查询至毫秒级,系统整体吞吐量提升约30%。 实时数仓与Web3: 基于Flink/Kafka构建实时ETL与滑动窗口聚合管道,精通ClickHouse多维分析;基于Go/go-ethereum开发Web3钱包后端,实现链上监听、Nonce/Gas管理及资金对账闭环。 AI辅助与DevOps: 熟练搭建K8s/AWS部署与Prometheus+Grafana监控体系;重度使用Cursor/Copilot辅助研发,将单元测试覆盖率从45%提升至78%。 擅长: 后端与微服务: 精通Java (JVM/Spring Cloud) 与Go (Gin);熟悉TCC、DDD、Sharding-JDBC、Kafka/RocketMQ…
#招聘 https://x.com/david_metaworld/status/2102428050474647751?s=46
#招聘 Top.Market - RWA https://x.com/the_Topmarket #全职 #增长 #运营 增长运营 ✅远程 #global 投递 @johnTopMarket ✅企业邮箱已认证 详情 https://abetterpath.notion.site/3e384271ff5581fdab43ee9116128c7c?pvs=74
Showing the 12 most recent of 309 posts we hold for @abetterpathxyz. 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.
Posts edited after publishing
@abetterpathxyz edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 28 August 2026
- Most recent edit
- 28 August 2026
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 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.
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.
@DeJob_official · 46,726#1
@TGWEBCN · 9,406#2
@TechFlowDaily · 18,726#3
@SmartDeerJobs · 4,361#4
@foresightnews · 18,046#5
@hrzzo1 · 3,981#6
@ferm_yiyi · 6,490#7
@remote_cn · 25,016#8
@chainfeedsxyz · 3,383#9
@SearchForTalents · 1,492 (as read 4 September 2026)#10
@ITJOBGEEK · 2,456#11
@haiwaiIt · 6,291#12
@godrealmx · 1,118#13
@bopinfabu · 3,493#14
@BTCdayu2 · 30,094#15
@sus_hhll · 4,735#16
@chaincatcher · 9,982#17
@keepondoing888 · 4,405#18
@yuancheng_job · 3,057#19
@yuanchengbangong · 8,135#20
@YCSL588 · 6,823#21
@HHJason123 · 8,539#22
@Bf36998 · 2,524#23
@siss67888 · 6,093#24
@OkTechnology · 560#25
@TopSekai · 2,827#26
@sleepingclub0 · 6,175#27
@shuangxiugognzuo · 6,687#28
@PAZP7 · 5,253#29
@PHJOBS001 · 2,188#30
@share_remote_jobs · 842#31
@tech6666 · 446#32
@rencaiphchannel · 574#33
@ITTECH008 · 2,346#34
@web3list · 1,415#35
@SSLL6698 · 2,072#36
@huhulc500 · 8,625#37
@HRAA899 · 4,270#38
@philippingwork · 3,766#39
@yokijob · 2,341#40
@makatizhipinz · 5,009#41
@beibei6868686 · 2,283#42
@ITejob · 2,610#43
@OBhrginnie · 3,911#44
@gojobph · 3,367#45
@fenghuangpindao · 2,792#46
@xbxiaobo_fyjszx · 1,346#47
@LDRhiring · 1,951#48
@Brokershire · 2,707#49
@jishuzhaopinpindao · 1,360#50
@zhaopin_jishu · 1,116#51
@OBstarshine · 4,511#52
@duidui007 · 2,198#53
@Lumenix_Jobs · 6,814#54
@JobYiqi888 · 2,707#55
@YZFC1699 · 1,101#56
@warming111 · 6,745#57
@Jerryleung030 · 1,361#58
@cryptojobhunter · 9,218#59
@theblockbeats · 37,492#60
@fionasdailynews · 6,755#61
@laolunote · 10,978#62
@ChannelPANews · 24,042#63
@wublock · 15,540#64
@toncoin_cn · 141,084#65
@BWEnews · 72,766#66
@globalcryptokol · 934#67
@bujidaodaily · 3,309#68
@followin_zh · 4,392#69
@lianqiujun · 12,900#70
@Odaily_News · 20,591#71
@Alex_xu_investment · 6,371#72
@POPIGOGO · 12,851#73
@SANYUANCapital · 933#74
@youmin88341 · 5,062#75
@Kunohr · 1,914#76
@drcdao666 · 6,054#77
@Solidleisure · 2,204#78
@BinanceSquareCN1 · 2,302#79
@HRZelda · 7,345#80
@jiuyicall · 11,661#81
@sunmoonzone · 2,207#82
@DeJob_Global · 16,563#83
@web3hiring · 61,058#84
@stablegram · 94,629#85
@cryptojobslist · 61,717#86
@degencryptojobs · 16,126#87
@illuminatiJOBS · 8,084#88
@onecryptofeed · 8,706#89
@web3jobopps · 9,079#90
Read from Telegram’s recommendation API, most recently 4 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.
@remote_cn · 25,016
Telegram ranks this channel #1 of 85 here — alongside 84 others — read 15 September 2026
@DeJob_official · 46,726
Telegram ranks this channel #1 of 94 here — alongside 93 others — read 27 August 2026
@BTCdayu2 · 30,094
Telegram ranks this channel #36 of 85 here — alongside 84 others — read 8 September 2026
@XCRLZP · 108,649
Telegram ranks this channel #41 of 82 here — alongside 81 others — read 13 August 2026
@BtokMedia · 288,827
Telegram ranks this channel #42 of 88 here — alongside 87 others — read 17 August 2026
@toncoin_cn · 141,084
Telegram ranks this channel #46 of 87 here — alongside 86 others — read 17 August 2026
@theblockbeats · 37,492
Telegram ranks this channel #52 of 92 here — alongside 91 others — read 1 September 2026
@outa_announcement · 27,557
Telegram ranks this channel #59 of 81 here — alongside 80 others — read 10 September 2026
@telonews_cn · 83,700
Telegram ranks this channel #59 of 65 here — alongside 64 others — read 18 August 2026
@ChannelPANews · 24,042
Telegram ranks this channel #64 of 96 here — alongside 95 others — read 17 September 2026
@binance_cn · 34,158
Telegram ranks this channel #67 of 84 here — alongside 83 others — read 3 September 2026
@OKXAnnouncements_CN · 44,940
Telegram ranks this channel #70 of 88 here — alongside 87 others — read 28 August 2026
@fenchacaij · 255,096
Telegram ranks this channel #75 of 83 here — alongside 82 others — read 17 August 2026
@web3hiring · 61,058
Telegram ranks this channel #79 of 95 here — alongside 94 others — read 22 August 2026
@cryptojobslist · 61,717
Telegram ranks this channel #87 of 95 here — alongside 94 others — read 22 August 2026
This channel appears in 15 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“abetterpath 招聘求职” (@abetterpathxyz), 33,176 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/abetterpathxyz.
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.