BIZTRAC BETA
Computer programming activities

MOONSHOT AS

Org. no. 930219479 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 132.0m
Operating profit NOK 131.7m
Equity NOK 122.0m
Incorporated 2022
Share capital NOK 40,000

Signals

1 flags
  • Nylig endring 2026-02-01 Adresseendring registrert 2026-02-01.

MOONSHOT AS is registered as a limited company in Oslo, Oslo with organisation number 930219479. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 1000000 shares. The company's stated purpose is: “Eie kryptovaluta og andre finansielle eiendeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 132.0m in revenue and NOK 131.7m in operating profit.

Key figures · 2024

Revenue
NOK 132.0m
Operating profit
NOK 131.7m
Equity
NOK 122.0m
Est. value
NOK 504.6m

Financial health · 2024

Liquidity
4.28
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.8%
Very good
Equity as a share of total capital

Who owns MOONSHOT AS?

NEVER SAY DIE AS
MOONSHOT AS
NOK 132.0m rev. · NOK 131.7m profit

MOONSHOT AS has 8 registered shareholders:

All shareholders and roles →

Which companies does MOONSHOT AS own?

MOONSHOT AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

MOONSHOT AS er morselskap for 3 datterselskaper:

Frequently asked questions about MOONSHOT AS

Who owns MOONSHOT AS?

NEVER SAY DIE AS is the largest registered owner, with 98.1%.

What is the revenue of MOONSHOT AS?

MOONSHOT AS had revenue of NOK 132.0m in 2024.

Who is the general manager of MOONSHOT AS?

Eirik Grøttum is registered as general manager of MOONSHOT AS.

Where is MOONSHOT AS based?

MOONSHOT AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.