BIZTRAC BETA
Computer programming activities

NEW MACHINE AS

Org. no. 923830030 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −85,000
Equity NOK −346,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−346k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

NEW MACHINE AS is registered as a limited company in Oslo, Oslo with organisation number 923830030. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og videreutvikling av applikasjoner og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −85,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −85,000
Equity
NOK −346,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-87.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NEW MACHINE AS?

MEGALO MEDIA AS
NEW MACHINE AS
NOK 0 rev. · NOK −85,000 profit

NEW MACHINE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEW MACHINE AS

Who owns NEW MACHINE AS?

MEGALO MEDIA AS is the largest registered owner, with 90.0%.

What is the revenue of NEW MACHINE AS?

NEW MACHINE AS had revenue of NOK 0 in 2025.

Who is the general manager of NEW MACHINE AS?

Adrian Eckbo Hoel is registered as general manager of NEW MACHINE AS.

Where is NEW MACHINE AS based?

NEW MACHINE 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.