BIZTRAC BETA
Construction of residential and non-residential buildings

FINNBUAN AS

Org. no. 924674962 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −302,000
Equity NOK 23.1m
Incorporated 2020
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−302k kr).

FINNBUAN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924674962. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 1.1m, divided into 30000 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskaper, samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −302,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −302,000
Equity
NOK 23.1m
Est. value
NOK 86.6m

Financial health · 2024

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

Who owns FINNBUAN AS?

SVAVA AS
FINNBUAN AS
NOK 0 rev. · NOK −302,000 profit

FINNBUAN AS has 5 registered shareholders:

All shareholders and roles →

Which companies does FINNBUAN AS own?

FINNBUAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FINNBUAN AS

Who owns FINNBUAN AS?

SVAVA AS is the largest registered owner, with 20.0%.

What is the revenue of FINNBUAN AS?

FINNBUAN AS had revenue of NOK 0 in 2024.

Who is the general manager of FINNBUAN AS?

Karl Johan Kopreitan is registered as general manager of FINNBUAN AS.

Where is FINNBUAN AS based?

FINNBUAN AS has its business address in Trondheim.

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.