biztrac. BETA
COMPANY REGISTER PROFILE
935881102 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

AMADEA AS

Org. no. 935881102 Limited company (AS) Asker Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −45,000
Equity NOK −9,000
Incorporated 2025
Share capital NOK 43,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).

AMADEA AS is registered as a limited company in Asker, Akershus with organisation number 935881102. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 43,000, divided into 42500 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK −9,000

Financial health · 2025

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-21.5%
Weak
Equity as a share of total capital

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

Who owns AMADEA AS?

AMADEA AS
NOK 0 rev. · NOK −45,000 profit

AMADEA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMADEA AS

Who owns AMADEA AS?

SUNBIRCH CAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of AMADEA AS?

AMADEA AS had revenue of NOK 0 in 2025.

Who is the general manager of AMADEA AS?

Fredric Lundgaard is registered as general manager of AMADEA AS.

Where is AMADEA AS based?

AMADEA AS has its business address in Heggedal.

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

Report a problem

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