diaObjectId
313963405517520945

150.806879, 0.916734

Discovery Date: 2026-01-09 07:34:48 UTC
Discovery MJD: 61049.32
Disc g-Flux: -2509.52±445.31
Latest Date: 2026-02-24 03:51:24 UTC
Latest MJD: 61095.16
Latest g-Flux: -1373.14±305.20
Peak Flux 3315.36±602.39 (z-band)
UTC at Peak 2026-02-20 04:25:26
MJD at Peak 61091.18
Detection Count 8
Equatorial Lon,Lat 10:03:13.651, 00:55:0.244
Galactic Lon,Lat 238.769393, 41.917041
Ecliptic Lon,Lat 152.529630, -10.329792
E(B-V) Extinction 0.024500
Duplicate diaObjects

Transient Name Server

This transient has probably not been reported to the TNS as yet. Check the TNS directly at this location.

Sherlock Contextual Classification

Prediction: Nuclear Transient

The transient is synonymous with 2MASXJ10031370%2B0054597; an r=16.33 mag galaxy found in the NED/SDSS catalogues. Its located 1.0" (1.8 Kpc) from the galaxy core. A host z=0.097 implies a m - M = 38.24.

Difference Image Lightcurve

Access the data from this plot in the LSST Alert Packet Data table below.
Learn how to interact with this plot.

Context Map

Recent Image Stamps

target

reference

difference

External Resources

Alerce Antares DECaLS Fink NED SIMBAD ZTF

LSST Alert Packet Data

MJD UTC band target diff flux reliability images alert packet
61095.160696 2026-02-24 03:51:24 r -1373 ± 305 0.21 target ref diff data
61095.121510 2026-02-24 02:54:58 z -4835 ± 668 0.28 target ref diff data
61094.191309 2026-02-23 04:35:29 r -4607 ± 413 0.45 target ref diff data
61094.177768 2026-02-23 04:15:59 z -4961 ± 794 0.15 target ref diff data
61091.207861 2026-02-20 04:59:19 g -2799 ± 549 0.20 target ref diff data
61091.184329 2026-02-20 04:25:26 z 3315 ± 602 0.18 target ref diff data
61049.316235 2026-01-09 07:35:22 g -3457 ± 449 0.25 target ref diff data
61049.315836 2026-01-09 07:34:48 g -2510 ± 445 0.20 target ref diff data
MJD filter magpsf magpsf_error flux_status
Need Help?

Start with our documentation on readthedocs, you might find the FAQ section especially useful.

If you still have questions, want to report a bug, or make a feature request, please reach out to us on the Lasair topic on the Rubin Community pages.

 readthedocs Lasair Community
Help