BIZTRAC BETA
COMPANY REGISTER PROFILE
982739667 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

SKAVANGERSKOGEN SAMEIE

Org. no. 982739667 Condominium flat owner (ESEK) Kongsberg Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 416,000
Operating profit NOK 116,000
Equity NOK 1.0m
Incorporated 1999

SKAVANGERSKOGEN SAMEIE is registered as a condominium flat owner in Kongsberg, Buskerud with organisation number 982739667. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1999. The most recent filed accounts, for the 2025 financial year, show NOK 416,000 in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 416,000
Operating profit
NOK 116,000
Equity
NOK 1.0m
Est. value
NOK 950,000

Financial health · 2025

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

Who owns SKAVANGERSKOGEN SAMEIE?

No shareholders are registered for SKAVANGERSKOGEN SAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SKAVANGERSKOGEN SAMEIE

What is the revenue of SKAVANGERSKOGEN SAMEIE?

SKAVANGERSKOGEN SAMEIE had revenue of NOK 416,000 in 2025.

Where is SKAVANGERSKOGEN SAMEIE based?

SKAVANGERSKOGEN SAMEIE has its business address in Kongsberg.

Property

Business address c/o KBBL Christian Augusts gate 4, 3611 Kongsberg
Cadastral unit 3303-7823/1/0/0

93 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.