BIZTRAC BETA
Development of building projects

SUNDEODDEN AS

Org. no. 922324735 Limited company (AS) Flekkefjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 1.2m
Incorporated 2019
Share capital NOK 1.5m

Signals

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

SUNDEODDEN AS is registered as a limited company in Flekkefjord, Agder with organisation number 922324735. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Kjøp, forvaltning,utvikling, utleie og salg av fast eiendom, herunder gjennom underliggende eiendomsselskaper. Dette er ingen begrensning. Selskapet skal også jobbe for å finne andre produkter for kjøp og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 1.2m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns SUNDEODDEN AS?

MODALSLI RØR HOLDING AS
SUNDEODDEN AS
NOK 0 rev. · NOK −15,000 profit

SUNDEODDEN AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUNDEODDEN AS

Who owns SUNDEODDEN AS?

MODALSLI RØR HOLDING AS is the largest registered owner, with 16.7%.

What is the revenue of SUNDEODDEN AS?

SUNDEODDEN AS had revenue of NOK 0 in 2025.

Who is the general manager of SUNDEODDEN AS?

Frank Tommy Strømland is registered as general manager of SUNDEODDEN AS.

Where is SUNDEODDEN AS based?

SUNDEODDEN AS has its business address in Flekkefjord.

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.