RingCentral CEO granted 140,207 performance units

RingCentral, Inc. CEO and Chairman Vladimir Shmunis reported an equity award of 140,207 Class A shares in the form of performance-based restricted stock units (PSUs).

Rhea-AI Filing Summary

RingCentral, Inc. CEO and Chairman Vladimir Shmunis reported an equity award of 140,207 Class A shares in the form of performance-based restricted stock units (PSUs). These PSUs reflect above-target achievement of 2025 performance goals certified on February 10, 2026.

All 140,207 shares subject to this first tranche will vest on February 21, 2026, tied to 2025 performance under a PSU grant originally awarded on May 20, 2025. After this acquisition, Shmunis directly beneficially owns 402,447 shares of RingCentral Class A Common Stock.

Insider Trade Summary

Grant/Award: 140,207 shares

Grant/Award 1 txn

Insider Shmunis Vladimir

Role CEO and Chairman

Type	Security	Shares	Price	Value
Grant/Award	Class A Common Stock	140,207	$0.00	$0.00

Holdings After Transaction: Class A Common Stock — 402,447 shares (Direct)

Footnotes (1)

1. F1. Represents performance-based restricted stock units ("PSUs"). The number of shares reported is the above-target achievement of certain performance goals, as certified by the Issuer's Compensation Committee on February 10, 2026, with respect to the first tranche of the performance awards granted to the Reporting Person on May 20, 2025. All shares reported will vest on February 21, 2026 and relate to the portion of this PSU grant that was based on 2025 performance. The remaining PSUs subject to this award will be eligible to vest based on 2026 performance.

FAQ

AI-generated questions and answers. How Rhea-AI works. Not financial advice.

What insider transaction did RingCentral (RNG) report for Vladimir Shmunis?

RingCentral CEO and Chairman Vladimir Shmunis reported acquiring 140,207 Class A shares via performance-based restricted stock units. These PSUs were earned for above-target 2025 performance and increase his directly owned Class A share balance to 402,447 after the transaction.

How many RingCentral (RNG) shares does Vladimir Shmunis own after this Form 4?

After the reported PSU acquisition, Vladimir Shmunis beneficially owns 402,447 shares of RingCentral Class A Common Stock directly. This total includes the 140,207 performance-based restricted stock units that were credited to him for above-target achievement of 2025 performance goals.

What are the key terms of the 140,207 PSUs reported by RingCentral (RNG)?

The 140,207 units are performance-based restricted stock units tied to 2025 goals. Above-target results were certified by RingCentral’s Compensation Committee on February 10, 2026, and all shares from this first tranche are scheduled to vest on February 21, 2026, subject to the award terms.

When will Vladimir Shmunis’s newly reported RingCentral (RNG) PSUs vest?

All 140,207 performance-based restricted stock units reported will vest on February 21, 2026. This tranche relates specifically to 2025 performance under a PSU grant originally made on May 20, 2025, with remaining units eligible to vest based on 2026 performance results.

What performance period do the reported RingCentral (RNG) PSUs cover?

The 140,207 PSUs relate to the portion of a May 20, 2025 grant based on 2025 performance. RingCentral’s Compensation Committee certified above-target achievement of certain goals on February 10, 2026, and remaining PSUs under this award may vest depending on 2026 performance outcomes.

Is the RingCentral (RNG) Form 4 transaction a purchase or an equity award?

The transaction is an equity award, not an open-market purchase. Vladimir Shmunis received 140,207 Class A shares through a grant of performance-based restricted stock units, recorded at a price of $0 per share, reflecting above-target performance rather than a cash share purchase.

AI-generated analysis. How Rhea-AI works. Not financial advice.

Form 4 Insider Transactions: What Each Field Means →

See more from StockTitan in Google Search and AI answers. Adds StockTitan as a preferred source · opens Google

Add on Google Not now

Accepted by SEC EDGAR 02/12/2026 - 07:44 PM EST Learn about SEC filing dates

SEC Form 4

FORM 4

UNITED STATES SECURITIES AND EXCHANGE COMMISSION
Washington, D.C. 20549

STATEMENT OF CHANGES IN BENEFICIAL OWNERSHIP

Filed pursuant to Section 16(a) of the Securities Exchange Act of 1934
or Section 30(h) of the Investment Company Act of 1940

OMB APPROVAL

OMB Number:			3235-0287
Estimated average burden
hours per response:			0.5

Check this box if no longer subject to Section 16. Form 4 or Form 5 obligations may continue. See Instruction 1(b).

Check this box to indicate that a transaction was made pursuant to a contract, instruction or written plan for the purchase or sale of equity securities of the issuer that is intended to satisfy the affirmative defense conditions of Rule 10b5-1(c). See Instruction 10.

1. Name and Address of Reporting Person^*

Shmunis Vladimir

(Last) (First) (Middle)

C/O RINGCENTRAL, INC.

20 DAVIS DRIVE

(Street)

BELMONT CA 94002

(City) (State) (Zip)

2. Issuer Name and Ticker or Trading Symbol
RingCentral, Inc. [ RNG ]

5. Relationship of Reporting Person(s) to Issuer
(Check all applicable)

X	Director		10% Owner
X	Officer (give title below)		Other (specify below)
	CEO and Chairman

3. Date of Earliest Transaction (Month/Day/Year)
02/10/2026

4. If Amendment, Date of Original Filed (Month/Day/Year)

6. Individual or Joint/Group Filing (Check Applicable Line)

X	Form filed by One Reporting Person
	Form filed by More than One Reporting Person

Table I - Non-Derivative Securities Acquired, Disposed of, or Beneficially Owned
1. Title of Security (Instr. 3)	2. Transaction Date (Month/Day/Year)	2A. Deemed Execution Date, if any (Month/Day/Year)	3. Transaction Code (Instr. 8)		4. Securities Acquired (A) or Disposed Of (D) (Instr. 3, 4 and 5)			5. Amount of Securities Beneficially Owned Following Reported Transaction(s) (Instr. 3 and 4)	6. Ownership Form: Direct (D) or Indirect (I) (Instr. 4)	7. Nature of Indirect Beneficial Ownership (Instr. 4)
			Code	V	Amount	(A) or (D)	Price
Class A Common Stock	02/10/2026		A		140,207(1)	A	$0	402,447	D

Table II - Derivative Securities Acquired, Disposed of, or Beneficially Owned (e.g., puts, calls, warrants, options, convertible securities)
1. Title of Derivative Security (Instr. 3)	2. Conversion or Exercise Price of Derivative Security	3. Transaction Date (Month/Day/Year)	3A. Deemed Execution Date, if any (Month/Day/Year)	4. Transaction Code (Instr. 8)		5. Number of Derivative Securities Acquired (A) or Disposed of (D) (Instr. 3, 4 and 5)		6. Date Exercisable and Expiration Date (Month/Day/Year)		7. Title and Amount of Securities Underlying Derivative Security (Instr. 3 and 4)		8. Price of Derivative Security (Instr. 5)	9. Number of derivative Securities Beneficially Owned Following Reported Transaction(s) (Instr. 4)	10. Ownership Form: Direct (D) or Indirect (I) (Instr. 4)	11. Nature of Indirect Beneficial Ownership (Instr. 4)
				Code	V	(A)	(D)	Date Exercisable	Expiration Date	Title	Amount or Number of Shares

Explanation of Responses:

1. Represents performance-based restricted stock units ("PSUs"). The number of shares reported is the above-target achievement of certain performance goals, as certified by the Issuer's Compensation Committee on February 10, 2026, with respect to the first tranche of the performance awards granted to the Reporting Person on May 20, 2025. All shares reported will vest on February 21, 2026 and relate to the portion of this PSU grant that was based on 2025 performance. The remaining PSUs subject to this award will be eligible to vest based on 2026 performance.

	/s/ John Marlow, Attorney-in-fact	02/12/2026
	** Signature of Reporting Person	Date
Reminder: Report on a separate line for each class of securities beneficially owned directly or indirectly.
* If the form is filed by more than one reporting person, see Instruction 4 (b)(v).
** Intentional misstatements or omissions of facts constitute Federal Criminal Violations See 18 U.S.C. 1001 and 15 U.S.C. 78ff(a).
Note: File three copies of this Form, one of which must be manually signed. If space is insufficient, see Instruction 6 for procedure.
Persons who respond to the collection of information contained in this form are not required to respond unless the form displays a currently valid OMB Number.