What you need to know
- Apple will host its Q1 2022 earnings call on Thursday, January 27, 2022.
- The call will kick off at 2:00 p.m. PDT / 5:00 p.m. EDT
Apple will host its first-quarter results for 2022 in a conference call that is scheduled to take place on Thursday, January 27, 2022. The call, which usually features Apple's Chief Executive Officer Tim Cook and Chief Financial Officer Luca Maestri, is currently scheduled to kick off at 2:00 p.m. PDT / 5:00 p.m. EDT.
Apple has provided the details of the call on the Apple Investor Relations (opens in new tab) website:
As usual, Apple notes that the call may contain forward-looking statements that are subject to change.
Apple also notes that, in order to stream the call, uses will need an iPhone, iPad, or iPod touch using Safari on iOS 12 or later. Mac users will need Safari running on macOS Mojave 10.14 or later. Apple TV owners will need a 2nd generation Apple TV or later. They also point out that PC users will require a browser like Chrome, Firefox, or Edge in order to stream the call.
Those interested in tuning in to listen to the conference call can do so by heading over to the Apple Earnings Call (opens in new tab) website. Apple will stream the call to the site live when it kicks off on January 27.
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.