BIZTRAC BETA
Rental and operating of own or leased real estate

AS KLAVENESSBYGG

Org. no. 930494003 Limited company (AS) Sandefjord Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 497,000
Equity NOK 55,000
Incorporated 1981
Share capital NOK 250,000

Signals

1 flags
  • Nylig endring 2026-02-05 Adresseendring registrert 2026-02-05.

AS KLAVENESSBYGG is registered as a limited company in Sandefjord, Vestfold with organisation number 930494003. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1981. Registered share capital is NOK 250,000. The company's stated purpose is: “Eie og drive forretningseiendommer og deltagelse i andre selskaper samt handel og produksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 497,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 497,000
Equity
NOK 55,000
Est. value
NOK 784,000

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.3%
Weak
Equity as a share of total capital

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

Who owns AS KLAVENESSBYGG?

BJØRN KLAVENESS
AS KLAVENESSBYGG
NOK 2.0m rev. · NOK 497,000 profit

AS KLAVENESSBYGG has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS KLAVENESSBYGG

Who owns AS KLAVENESSBYGG?

BJØRN KLAVENESS is the largest registered owner, with 66.8%.

What is the revenue of AS KLAVENESSBYGG?

AS KLAVENESSBYGG had revenue of NOK 2.0m in 2025.

Who is the general manager of AS KLAVENESSBYGG?

Bjørn Klaveness is registered as general manager of AS KLAVENESSBYGG.

Where is AS KLAVENESSBYGG based?

AS KLAVENESSBYGG has its business address in Sandefjord.

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.