BIZTRAC BETA
Development of building projects

TROMSØ UTBYGGING AS

Org. no. 990424683 Limited company (AS) Tromsø Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 309,000
Incorporated 2006
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TROMSØ UTBYGGING AS is registered as a limited company in Tromsø, Troms with organisation number 990424683. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Prosjektutvikling i egen regi.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 309,000
Est. value
NOK 282,000

Financial health · 2024

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

Who owns TROMSØ UTBYGGING AS?

MÆLEN HOLDING AS
TROMSØ UTBYGGING AS
NOK 0 rev. · NOK −15,000 profit

TROMSØ UTBYGGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROMSØ UTBYGGING AS

Who owns TROMSØ UTBYGGING AS?

MÆLEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TROMSØ UTBYGGING AS?

TROMSØ UTBYGGING AS had revenue of NOK 0 in 2024.

Who is the general manager of TROMSØ UTBYGGING AS?

Einar Sørensen is registered as general manager of TROMSØ UTBYGGING AS.

Where is TROMSØ UTBYGGING AS based?

TROMSØ UTBYGGING AS has its business address in Tromsø.

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.