Atlassian CTO sells 3,072 shares for tax cover

Atlassian Corp Chief Technology Officer Rajeev Bashyam reported selling 3,072 shares of Class A common stock in open-market transactions.

Rhea-AI Filing Summary

Atlassian Corp Chief Technology Officer Rajeev Bashyam reported selling 3,072 shares of Class A common stock in open-market transactions. The sales occurred on February 19, 2026 and were executed solely to cover tax withholding obligations arising from the vesting and settlement of restricted stock units, according to the filing.

The transactions were described as "sell to cover" and not discretionary trades by the executive. After these sales, Bashyam directly owned 212,916 shares of Atlassian Class A common stock.

Insider Trade Summary

Net Seller: 3,072 shares

Net Sell 4 txns

Insider RAJAN RAJEEV BASHYAM

Role Chief Technology Officer

Sold 3,072 shs ($250K)

Type	Security	Shares	Price	Value
Sale	Class A Common Stock	1,297	$80.5662	$104K
Sale	Class A Common Stock	379	$82.6035	$31K
Sale	Class A Common Stock	1,321	$81.6349	$108K
Sale	Class A Common Stock	75	$83.5503	$6K

Holdings After Transaction: Class A Common Stock — 212,916 shares (Direct)

Footnotes (5)

1. F1. The sale reported on this Form 4 represents shares sold by the Reporting Person to cover tax withholding obligations in connection with the vesting and settlement of RSUs. The sale was to satisfy tax withholding obligations to be funded by a "sell to cover" transaction and does not represent a discretionary transaction by the Reporting Person.
2. F2. This transaction was executed in multiple trades during the day at prices ranging from $80.22 to $81.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.
3. F3. This transaction was executed in multiple trades during the day at prices ranging from $82.22 to $83.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.
4. F4. This transaction was executed in multiple trades during the day at prices ranging from $81.22 to $82.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.
5. F5. This transaction was executed in multiple trades during the day at prices ranging from $83.22 to $83.93. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.

FAQ

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

What insider transaction did Atlassian (TEAM) CTO Rajeev Bashyam report?

Atlassian CTO Rajeev Bashyam reported selling 3,072 Class A shares. The shares were sold on February 19, 2026 in open-market transactions to cover tax withholding obligations tied to RSU vesting, rather than as discretionary stock sales.

Why did Atlassian (TEAM) CTO Rajeev Bashyam sell 3,072 shares?

The shares were sold to cover tax withholding obligations from vesting and settlement of RSUs. The filing states these were "sell to cover" transactions specifically to fund taxes and do not represent discretionary trading decisions by the reporting person.

How many Atlassian (TEAM) shares does Rajeev Bashyam hold after this Form 4?

After the reported sales, Rajeev Bashyam directly owns 212,916 Atlassian Class A shares. This post-transaction balance reflects the net holdings following the 3,072 shares sold to satisfy RSU-related tax withholding obligations on February 19, 2026.

On what date did the Atlassian (TEAM) insider sales by Rajeev Bashyam occur?

All reported transactions occurred on February 19, 2026. Multiple trades that day reduced his holdings by a total of 3,072 Atlassian Class A shares, executed as open-market sales to cover tax obligations from RSU vesting and settlement.

Were the Atlassian (TEAM) share sales by CTO Rajeev Bashyam discretionary trades?

No, the filing states the sales were not discretionary. They were executed under a "sell to cover" arrangement specifically to satisfy tax withholding obligations arising from RSU vesting, rather than elective buying or selling decisions by the executive.

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/20/2026 - 06:00 PM 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^*

RAJAN RAJEEV BASHYAM

(Last) (First) (Middle)

C/O ATLASSIAN CORPORATION

350 BUSH STREET, FLOOR 13

(Street)

SAN FRANCISCO CA 94104

(City) (State) (Zip)

2. Issuer Name and Ticker or Trading Symbol
Atlassian Corp [ TEAM ]

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

	Director		10% Owner
X	Officer (give title below)		Other (specify below)
	Chief Technology Officer

3. Date of Earliest Transaction (Month/Day/Year)
02/19/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/19/2026		S(1)		1,297	D	$80.5662(2)	214,691	D
Class A Common Stock	02/19/2026		S(1)		379	D	$82.6035(3)	214,312	D
Class A Common Stock	02/19/2026		S(1)		1,321	D	$81.6349(4)	212,991	D
Class A Common Stock	02/19/2026		S(1)		75	D	$83.5503(5)	212,916	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. The sale reported on this Form 4 represents shares sold by the Reporting Person to cover tax withholding obligations in connection with the vesting and settlement of RSUs. The sale was to satisfy tax withholding obligations to be funded by a "sell to cover" transaction and does not represent a discretionary transaction by the Reporting Person.

2. This transaction was executed in multiple trades during the day at prices ranging from $80.22 to $81.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.

3. This transaction was executed in multiple trades during the day at prices ranging from $82.22 to $83.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.

4. This transaction was executed in multiple trades during the day at prices ranging from $81.22 to $82.21. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.

5. This transaction was executed in multiple trades during the day at prices ranging from $83.22 to $83.93. The Reporting Person hereby undertakes to provide upon request to the SEC staff, the issuer or a security holder of the issuer full information regarding the number of shares and prices at which the transactions were effected.

Remarks:

	/s/ Veena Bhatia, Attorney-in-Fact for RAJAN RAJEEV BASHYAM	02/20/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.