Time series / Model
Chronos (T5)
- Organisation
- Amazon
- Family
- Chronos · version 1.0
- Released
- 2024-03-13 (Repository README news entry '13 Mar 2024: Chronos paper and inference code released' (https://raw.githubusercontent.com/amazon-science/chronos-forecasting/main/README.md); arXiv v1 submitted 12 Mar 2024 (https://arxiv.org/abs/2403.07815))
- Checkpoints
- amazon/chronos-t5-tiny, amazon/chronos-t5-mini, amazon/chronos-t5-small, amazon/chronos-t5-base, amazon/chronos-t5-large
- Weights
- Open · apache-2.0
- Links
- PaperModel cardCode
Training data disclosure: Full list
Level determined for 100% of benchmark cells.
- TestTest data seen0
- SeenSeen, split unclear8
- TrainTraining data seen0
- Related data seen1
- NoNot seen40
- ?Unknown0
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Training corpora
-
Chronos training corpus (real-world datasets)
· 28 sources (complete list) · pre-training
· homepage
Evidence that Chronos (T5) uses it
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
arxiv.org · paper · Section 5.1 · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 Contents of this corpus
-
Brazilian Cities Temperature · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Brazilian Cities Temperature”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Mexico City Bikes · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Mexico City Bikes”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
NREL Solar Power Data for Integration Studies (2006) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Solar (5 Min.)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
NREL Solar Power Data for Integration Studies (2006) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Solar (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Spanish Energy and Weather · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Spanish Energy and Weather”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Taxi (Hourly) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Taxi (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
USHCN · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“USHCN”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Weatherbench (Daily) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Weatherbench (Daily)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Weatherbench (Hourly) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Weatherbench (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Weatherbench (Weekly) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Weatherbench (Weekly)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Wiki Daily (100k) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Wiki Daily (100k)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Wind Farms (Daily) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Wind Farms (Daily)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Wind Farms (Hourly) · split: unknown
Pretraining-only dataset (not part of Chronos Benchmark I/II). The paper does not state explicitly that the full series were used, but describes no held-out portion for this group.
Evidence
“Wind Farms (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Pretraining-only' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
ElectricityLoadDiagrams20112014 (UCI) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Electricity (15 Min.)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Electricity (ECL, 321 clients) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Electricity (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Electricity Weekly (Monash) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Electricity (Weekly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
KDD Cup 2018 · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“KDD Cup 2018”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
London Smart Meters · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“London Smart Meters”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
M4 Daily · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“M4 (Daily)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
M4 Hourly · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“M4 (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
M4 Monthly · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“M4 (Monthly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
M4 Weekly · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“M4 (Weekly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Pedestrian Counts · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Pedestrian Counts”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Rideshare · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Rideshare”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Taxi (30 Min.) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Taxi (30 Min.)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Temperature Rain · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Temperature-Rain”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Uber TLC (Daily) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Uber TLC (Daily)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Uber TLC (Hourly) · split: train
Chronos Benchmark I (in-domain) dataset: used for training except the last H observations of each series (H is task-specific, Table 3), which are held out for testing. This is the Chronos paper's own split, not GIFT-Eval's or long-horizon's.
Evidence
“Uber TLC (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'In-domain evaluation' · retrieved 2026-10-15 “pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15
-
Brazilian Cities Temperature · split: unknown
Other declared training data
-
TSMixup · split: unknown
Synthetic augmentation: convex combinations of series sampled from the 28 real training datasets (10M series; HF config training_corpus_tsmixup_10m). Sampled 9:1 with KernelSynth data.
Evidence
“on 10M TSMixup augmentations (see Section 4.1) generated from the 28 training datasets, with K = 3 in Algorithm 1, and 1M synthetic time series generated using Gaussian processes (see Section 4.2)”
arxiv.org · paper · Section 5.2 · retrieved 2026-10-15 “10M TSMixup augmentations of real-world data”
huggingface.co · dataset card · Section 'Chronos training corpus with TSMixup & KernelSynth' · retrieved 2026-10-15 -
KernelSynth · split: unknown
Purely synthetic Gaussian-process data (1M series; HF config training_corpus_kernel_synth_1m).
Evidence
“KernelSynth, a method to generate synthetic time series using Gaussian processes (GPs).”
arxiv.org · paper · Section 4.2 · retrieved 2026-10-15 “1M synthetic time series generated with KernelSynth”
huggingface.co · dataset card · Section 'Chronos training corpus with TSMixup & KernelSynth' · retrieved 2026-10-15
Declared exclusions
-
Dataset Car Parts · entirely excluded
Evidence
“Car Parts”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset COVID Deaths · entirely excluded
Evidence
“Covid Deaths”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset ETTm1 · entirely excluded
Evidence
“ETT (15 Min.)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset ETTm2 · entirely excluded
Evidence
“ETT (15 Min.)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset ETTh1 · entirely excluded
Evidence
“ETT (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset ETTh2 · entirely excluded
Evidence
“ETT (Hourly)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset Exchange-Rate · entirely excluded
Evidence
“Exchange Rate”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset Hospital · entirely excluded
Evidence
“Hospital”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset M4 Quarterly · entirely excluded
Evidence
“M4 (Quarterly)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset M4 Yearly · entirely excluded
Evidence
“M4 (Yearly)”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15 -
Dataset Traffic (PeMS San Francisco Bay, 862 sensors) · entirely excluded
Evidence
“Traffic”
arxiv.org · paper · Appendix B, Table 3, section 'Zero-shot evaluation' · retrieved 2026-10-15 “zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
arxiv.org · paper · Appendix B, Table 3 caption · retrieved 2026-10-15
Benchmark cells
GIFT-Eval
Not seen Jena Weather (GIFT-Eval) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen BizITObs - Application · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen BizITObs - Service · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen BizITObs - L2C · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Bitbrains - Fast Storage · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Bitbrains - rnd · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Restaurant (Recruit Restaurant Visitor Forecasting) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen ETT1 (GIFT-Eval) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen ETT2 (GIFT-Eval) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Loop Seattle (LibCity) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen SZ-Taxi (LibCity) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen M_DENSE (LibCity) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Solar (LSTNet, 137 Alabama PV plants) · related dataset NREL Solar Power Data for Integration Studies (2006) was used (via Chronos training corpus (real-world datasets))
Evidence (6)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“Solar (5 Min.)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“The uploaded dataset contains the aggregated version of a subset of the original dataset used by Lai et al. (2017).”
“Solar (5 Min., Hourly) contains data about solar power generation in the US in 2006. The original data has 5 minute frequency and was obtained from https://www.nrel.gov/grid/solar-power-data.html”
Not seen Hierarchical Sales (Mancuso et al., 2020) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen M4 Yearly · the authors state the dataset was excluded from training
Evidence (2)
“M4 (Yearly)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen M4 Quarterly · the authors state the dataset was excluded from training
Evidence (2)
“M4 (Quarterly)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Seen, split unclear M4 Monthly · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“M4 (Monthly)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Seen, split unclear M4 Weekly · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“M4 (Weekly)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Seen, split unclear M4 Daily · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“M4 (Daily)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Seen, split unclear M4 Hourly · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“M4 (Hourly)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Not seen Hospital · the authors state the dataset was excluded from training
Evidence (2)
“Hospital”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen COVID Deaths · the authors state the dataset was excluded from training
Evidence (2)
“Covid Deaths”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen US Births · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Saugeen River Flow · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Seen, split unclear Temperature Rain · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“Temperature-Rain”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Seen, split unclear KDD Cup 2018 · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“KDD Cup 2018”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Not seen Car Parts · the authors state the dataset was excluded from training
Evidence (2)
“Car Parts”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Seen, split unclear ElectricityLoadDiagrams20112014 (UCI) · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“Electricity (15 Min.)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Long-horizon forecasting (ETT, Electricity, Traffic, Weather, Exchange, ILI)
Not seen ETTh1 · the authors state the dataset was excluded from training
Evidence (2)
“ETT (Hourly)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen ETTh2 · the authors state the dataset was excluded from training
Evidence (2)
“ETT (Hourly)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen ETTm1 · the authors state the dataset was excluded from training
Evidence (2)
“ETT (15 Min.)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen ETTm2 · the authors state the dataset was excluded from training
Evidence (2)
“ETT (15 Min.)”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Seen, split unclear Electricity (ECL, 321 clients) · a training split was used; its overlap with this benchmark's test data is not established (via Chronos training corpus (real-world datasets))
Evidence (4)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
“Electricity (Hourly)”
“pretraining-only data is only used for Chronos training; in-domain evalution data is used for training Chronos models and other task-specific baselines, except for the H observations that are held out for in-domain testing only”
Not seen Traffic (PeMS San Francisco Bay, 862 sensors) · the authors state the dataset was excluded from training
Evidence (2)
“Traffic”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen Weather (Jena, 2020; Autoformer) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Exchange-Rate · the authors state the dataset was excluded from training
Evidence (2)
“Exchange Rate”
“zero-shot evaluation data is not used in training Chronos models, but only for evaluation (final H observations), as well as for training task-specific baselines (excluding the final H observations)”
Not seen ILI (CDC influenza-like illness, national) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Time-series anomaly detection
Not seen TSB-AD-U (TSB-AD univariate) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen TSB-AD-M (TSB-AD multivariate) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen UCR Time Series Anomaly Archive (Hexagon ML/UCR, KDD Cup 2021) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Server Machine Dataset (SMD) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Mars Science Laboratory (MSL) telemetry anomaly dataset · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Soil Moisture Active Passive (SMAP) telemetry anomaly dataset · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Pooled Server Metrics (PSM) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Secure Water Treatment (SWaT) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Yahoo S5 Labeled Anomaly Detection Dataset (Yahoo Webscope S5) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen Numenta Anomaly Benchmark (NAB) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Time-series classification
Not seen UCR Time Series Classification Archive (2018) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Not seen UEA Multivariate Time Series Classification Archive (2018) · absent from the complete list of training data
Evidence (3)
“Overall, we used 28 datasets for training Chronos models, consisting of about 890K univariate time series with approximately 84B observations (tokens) in total.”
“The table is divided into three sections, representing how the datasets were used for Chronos models: in total, 55 datasets where used for experiments, 13 of which for pretraining only, 15 for in-domain evaluation, and 27 for zeroshot evaluation”
“The training corpus used for training the Chronos models can be loaded via the configs `training_corpus_tsmixup_10m` (10M TSMixup augmentations of real-world data) and `training_corpus_kernel_synth_1m` (1M synthetic time series generated with KernelSynth)”
Notes
Pre-trained on 10M TSMixup augmentations of the 28 real training datasets plus 1M KernelSynth series (ratio 9:1). Benchmark I (15 datasets) is in-domain: trained on all but the last H observations. Benchmark II (27 datasets, incl. ETT, Exchange Rate, Traffic, Weather) was not used for training. Electricity (15 Min./Hourly/Weekly) is in the training data (test window held out). The paper's footnote concedes Benchmark II start times are not guaranteed to be after the training data's last timestamp. Identical copies of the checkpoints exist under the autogluon/ HF org. Other stated exclusions, not tracked here: chronos-benchmark-ii (all); chronos-benchmark-i (test); Australian Electricity (all); CIF 2016 (all); Dominick (all); ERCOT Load (all); FRED-MD (all); M1 (Monthly) (all); M1 (Quarterly) (all); M1 (Yearly) (all); M3 (Monthly) (all); M3 (Quarterly) (all); M3 (Yearly) (all); M5 (all); NN5 (Daily) (all); NN5 (Weekly) (all); Tourism (Monthly) (all); Tourism (Quarterly) (all); Tourism (Yearly) (all); Weather (all).
Sources
- Chronos: Learning the Language of Time Series (arXiv v3, TMLR 10/2024) · paper · retrieved 2026-10-15
- amazon/chronos-t5-large model card · model card · retrieved 2026-10-15
- autogluon/chronos_datasets dataset card · dataset card · retrieved 2026-10-15
- amazon-science/chronos-forecasting README · readme · retrieved 2026-10-15