BIZTRAC BETA
Development of building projects

ANIDEI AS

Org. no. 814332012 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1
Equity NOK 2,000
Incorporated 2014
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1 kr).

ANIDEI AS is registered as a limited company in Frogn, Akershus with organisation number 814332012. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Gjennomføre direkte og indirekte eiendomsinvesteringer, samt forvalte, utvikle, leie ut og/eller avhende eiendomsinvesteringer og alt som står i forbindelse herved, herunder deltakelse i andre selskaper med lignende formål. I tillegg kan selskapet yte juridisk, markedsmessig og teknisk kompetanse med spesialrådgivning til andre aktører.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1
Equity
NOK 2,000
Est. value
NOK 2,000

Financial health · 2025

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

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

Who owns ANIDEI AS?

ELI KLYPEN MONSHAUGEN
ANIDEI AS
NOK 0 rev. · NOK −1 profit

ANIDEI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANIDEI AS

Who owns ANIDEI AS?

ELI KLYPEN MONSHAUGEN is the largest registered owner, with 40.0%.

What is the revenue of ANIDEI AS?

ANIDEI AS had revenue of NOK 0 in 2025.

Where is ANIDEI AS based?

ANIDEI AS has its business address in Drøbak.

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.