Company: FGMCU
Filing Date: 2025-12-11
Form Type: 425
Source: 0001104659-25-120350
Chunk: 0

Company: FG Merger II Corp.
Filing Date: 2025-12-11
Form: 425
Chunk 0
---
Filed by FG Merger II Corp.

pursuant to Rule 425 under the Securities Act of 1933

and deemed filed pursuant to Rule 14a-12

under the Securities Exchange Act of 1934

Subject Company: Boxabl Inc.

Commission File No. 000-56579

Date: December 11, 2025

As previously disclosed, on August 4, 2025, Boxabl Inc. (“Boxabl”)
entered into an Agreement and Plan of Merger (the “Merger Agreement”) by and among the Company, FG Merger II Corp., a Nevada
corporation (“FGMC”), and FG Merger Sub II Inc., a Nevada corporation and wholly-owned subsidiary of FGMC (“Merger Sub”).
The Merger Agreement provides for a two-step merger transaction (the “Mergers”) in which, first, Merger Sub will merge with
and into the Company (the “First Merger”), with the Company surviving as a wholly-owned subsidiary of FGMC, and, immediately
thereafter, the Company (as the surviving company in the First Merger) will merge with and into FGMC (the “Second Merger”),
with FGMC continuing as the surviving public company (the “Surviving Pubco”). By virtue of the consummation of the Mergers,
the Surviving Pubco will change its name to BOXABL Inc.

The following is a transcript of a conversation hosted by Christina
Ayanian of the Nasdaq MarketSite involving Martin Costas, Chief Financial Officer of Boxabl, published December 11, 2025.

Kristina Ayanian: From Nasdaq MarketSite. I'm your host, Christina
Ayanian. And joining me today is Martin Costas, Chief Financial Officer of Boxabl. Martin, great to see you again. Thank you so much for
joining.

Martin Costas:Thank you for inviting us.

Kristina Ayanian: Now, since we last caught up, a lot has happened.
Talk to me about your journey to going public and why now is the right time.

Yeah, well, we're very excited, actually. We managed to file our S4.
We're doing a SPAC with FGMC is the ticker. Uh, we filed the S-4 before the shutdown of the government. And now that today they announced
that this is done. We're very excited, especially because we are already subject to exchange. So, we have been reporting