Rubicon (RBTC) Form 4 Rubicon / Jose Miguel Enrich ownership change

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

1. Name and Address of Reporting Person^*

Enrich Jose Miguel

(Last) (First) (Middle)

781 CRANDON BLVD 902

(Street)

KEY BISCAYNE FL 33149

(City) (State) (Zip)

2. Issuer Name and Ticker or Trading Symbol
Rubicon Technologies, Inc. [ RBT ]

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

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

3. Date of Earliest Transaction (Month/Day/Year)
09/15/2023

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

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
Warrants (right to buy)	$0.01	09/15/2023		P		3,984,946		(1)	09/15/2026	Class A common Stock	3,984,946	(1)	3,984,946	I	By MBI Holdings LP(2)

Explanation of Responses:

1. On September 15, 2023, Rubicon Technologies, Inc. ("Issuer") entered into a securities purchase agreement with MBI Holdings LP ("MBI"), pursuant to which MBI purchased $1.8 million of warrants entitling MBI to purchase 3,984,946 shares of Class A Common Stock at an exercise price of $0.01 per share, exercisable at the option of MBI.

2. Mr. Enrich is the general partner of MBI and has voting and dispositive control over such securities and may be deemed to beneficially own such securities held by MBI. Mr. Enrich disclaims beneficial ownership of these securities except to the extent of his pecuniary interest therein.

	/s/ Jose Miguel Enrich	09/21/2023
	** 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.