Papers › Gaia and HST astrometry of the very massive ∼150 M_⊙ candidate runaway star VFTS682
Gaia and HST astrometry of the very massive ∼150 M_⊙ candidate runaway star VFTS682
M. Renzo, S. E. de Mink, D. J. Lennon, I. Platais, R. P. van der Marel, E. Laplace, J. M. Bestenlehner, C. J. Evans, V. Hénault-Brunet, S. Justham, A. de Koter, N. Langer, F. Najarro, F. R. N. Schneider, J. S. Vink
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
How very massive stars form is still an open question in astrophysics. VFTS682 is among the most massive stars known, with an inferred initial mass of ∼150 M_⊙ . It is located in 30 Doradus at a projected distance of 29 pc from the central cluster R136. Its apparent isolation led to two hypotheses: either it formed in relative isolation or it was ejected dynamically from the cluster. We investigate the kinematics of VFTS682 as obtained by Gaia and Hubble Space Telescope astrometry. We derive a projected velocity relative to the cluster of 38 ±17 km s⁻¹ (1σ confidence interval). Although the error bars are substantial, two independent measures suggest that VFTS682 is a runaway ejected from the central cluster. This hypothesis is further supported by a variety of circumstantial clues. The central cluster is known to harbor other stars more massive than 150 M_⊙ of similar spectral type and recent astrometric studies on VFTS16 and VFTS72 provide direct evidence that the cluster can eject some of its most massive members, in agreement with theoretical predictions. If future data confirm the runaway nature, this would make VFTS682 the most massive runaway star known to date.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections