BIZTRAC BETA
Development of building projects

KALDNES BRYGGE AS

Org. no. 971589019 Limited company (AS) Tønsberg Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 252.6m
Operating profit NOK 51.4m
Equity NOK 45.3m
Incorporated 1994
Share capital NOK 702,000

KALDNES BRYGGE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 971589019. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1994. Registered share capital is NOK 702,000, divided into 2888056 shares. The company's stated purpose is: “Eie, leie, utleie, utvikle, forvalte, drifte og investere i fast eiendom eller selskaper som eier fast eiendom, samt andre aktiviteter forbundet med dette, herunder oppta lån fra selskaper i samme konsern for å finansiere virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 252.6m in revenue and NOK 51.4m in operating profit.

Key figures · 2024

Revenue
NOK 252.6m
Operating profit
NOK 51.4m
Equity
NOK 45.3m
Est. value
NOK 156.0m

Financial health · 2024

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

Who owns KALDNES BRYGGE AS?

SELVAAG BOLIG ASA
KALDNES BRYGGE AS
NOK 252.6m rev. · NOK 51.4m profit

KALDNES BRYGGE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KALDNES BRYGGE AS own?

KALDNES BRYGGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KALDNES BRYGGE AS

Who owns KALDNES BRYGGE AS?

SELVAAG BOLIG ASA is the largest registered owner, with 50.0%.

What is the revenue of KALDNES BRYGGE AS?

KALDNES BRYGGE AS had revenue of NOK 252.6m in 2024.

Where is KALDNES BRYGGE AS based?

KALDNES BRYGGE AS has its business address in Tønsberg.

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.