Realized Volatility Forecasting for New Issues and Spin-Offs using Multi-Source Transfer Learning

Andreas Teller, Uta Pigorsch, Christian Pigorsch
3/16/2025
cs.LGq-fin.CP

No confident code implementation found for this paper.

Abstract

Forecasting the volatility of financial assets is essential for various financial applications. This paper addresses the challenging task of forecasting the volatility of financial assets with limited historical data, such as new issues or spin-offs, by proposing a multi-source transfer learning approach. Specifically, we exploit complementary source data of assets with a substantial historical data record by selecting source time series instances that are most similar to the limited target data of the new issue/spin-off. Based on these instances and the target data, we estimate linear and non-linear realized volatility models and compare their forecasting performance to forecasts of models trained exclusively on the target data, and models trained on the entire source and target data. The results show that our transfer learning approach outperforms the alternative models and that the integration of complementary data is also beneficial immediately after the initial trading day of the new issue/spin-off.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{teller2025realized,
  title  = {Realized Volatility Forecasting for New Issues and Spin-Offs using Multi-Source Transfer Learning},
  author = {Andreas Teller and Uta Pigorsch and Christian Pigorsch},
  year   = {2025},
  eprint = {2503.12648},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2503.12648v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2503.12648.svg)](https://codeofpaper.com/paper/2503.12648)

Discussion