RxSight, Inc. to Report First Quarter 2025 Financial Results on May 7, 2025

ALISO VIEJO, Calif., April 23, 2025 (GLOBE NEWSWIRE) -- (NASDAQ: RXST) – RxSight, Inc., an ophthalmic medical device company dedicated to providing high-quality customized vision to patients following cataract surgery, will report financial results for the first quarter of 2025 after the market close on Wednesday, May 7, 2025. The company’s management will discuss the results during a conference call beginning at 1:30 p.m. Pacific Time / 4:30 p.m. Eastern Time.

To participate in the conference call, please dial (800) 715-9871 or (646) 307-1963, and enter the conference code: 8740296. The call will also be broadcast live in listen-only mode via a link on the company’s investor relations website at https://investors.rxsight.com/. An archived recording of the call will be available through the same link shortly after its completion.

About RxSight, Inc.

RxSight, Inc. is an ophthalmic medical device company dedicated to providing high-quality customized vision to patients following cataract surgery. The RxSight® Light Adjustable Lens system, comprised of the RxSight Light Adjustable Lens® (LAL®/LAL+®, collectively the “LAL”), RxSight Light Delivery Device (LDD™) and accessories, is the first and only commercially available intraocular lens (IOL) technology that can be adjusted after surgery, enabling doctors to customize and deliver high-quality vision to patients after cataract surgery. Additional information about RxSight can be found at www.rxsight.com.

Company Contact:
Shelley B. Thunen
Chief Financial Officer
sthunen@rxsight.com

Investor Relations Contact:
Oliver Moravcevic
VP, Investor Relations
omoravcevic@rxsight.com

Legal Disclaimer:

EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.