Atlassian CRO sells 1,222 shares for tax withholding

Atlassian Corp Chief Revenue Officer Brian Duffy reported selling 1,222 shares of Class A Common Stock in open-market transactions.

Rhea-AI Filing Summary

Atlassian Corp Chief Revenue Officer Brian Duffy reported selling 1,222 shares of Class A Common Stock in open-market transactions. The sales took place on February 19, 2026 at prices generally between $80.22 and $83.93. According to the filing, these were automatic "sell to cover" transactions to satisfy tax withholding obligations related to vesting and settlement of restricted stock units, and were not discretionary trades. After these sales, Duffy directly owned 124,332 Atlassian shares.

Insider Trade Summary

Net Seller: 1,222 shares

Net Sell 4 txns

Insider DUFFY BRIAN

Role Chief Revenue Officer

Sold 1,222 shs ($99K)

Type	Security	Shares	Price	Value
Sale	Class A Common Stock	151	$82.6035	$12K
Sale	Class A Common Stock	525	$81.6349	$43K
Sale	Class A Common Stock	30	$83.5503	$3K
Sale	Class A Common Stock	516	$80.5662	$42K

Holdings After Transaction: Class A Common Stock — 124,332 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 $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.
3. F3. 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.
4. F4. 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.
5. F5. 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.

FAQ

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

What did Atlassian (TEAM) executive Brian Duffy report on this Form 4?

Brian Duffy, Atlassian’s Chief Revenue Officer, reported selling 1,222 shares of Class A Common Stock. The transactions were tied to tax withholding on vested RSUs rather than discretionary trading in the company’s stock.

How many Atlassian (TEAM) shares did Brian Duffy sell and at what prices?

The Form 4 shows sales totaling 1,222 Atlassian Class A shares. These open-market transactions occurred at various prices during the day, generally ranging from about $80.22 to $83.93 per share, according to the detailed pricing footnotes.

Why did Atlassian (TEAM) CRO Brian Duffy sell shares in this filing?

The filing explains the shares were sold solely to cover tax withholding obligations from the vesting and settlement of restricted stock units. It describes the activity as a "sell to cover" transaction, not a discretionary decision to reduce his Atlassian holdings.

How many Atlassian (TEAM) shares does Brian Duffy own after these transactions?

After completing the tax-related sales, Brian Duffy directly owned 124,332 shares of Atlassian Class A Common Stock. This post-transaction balance is stated in the Form 4 as the total number of shares held following the reported trades.

Were Brian Duffy’s Atlassian (TEAM) share sales executed in a single trade or multiple trades?

The Form 4 notes that the reported sales were executed in multiple trades throughout the day. Footnotes state price ranges for these trades and indicate full trade details are available on request to Atlassian, the SEC staff, or security holders.

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^*

DUFFY BRIAN

(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 Revenue 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)		151	D	$82.6035(2)	125,403	D
Class A Common Stock	02/19/2026		S(1)		525	D	$81.6349(3)	124,878	D
Class A Common Stock	02/19/2026		S(1)		30	D	$83.5503(4)	124,848	D
Class A Common Stock	02/19/2026		S(1)		516	D	$80.5662(5)	124,332	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 $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.

3. 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.

4. 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.

5. 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.

Remarks:

	/s/ Veena Bhatia, Attorney-in-Fact for DUFFY BRIAN	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.