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

SAMEIET KROSSNES

Org. no. 990224048 Condominium flat owner (ESEK) Haugesund Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 161,000
Operating profit NOK 27,000
Equity NOK 207,000
Incorporated 2004

SAMEIET KROSSNES is registered as a condominium flat owner in Haugesund, Rogaland with organisation number 990224048. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2004. The most recent filed accounts, for the 2025 financial year, show NOK 161,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2025

Revenue
NOK 161,000
Operating profit
NOK 27,000
Equity
NOK 207,000
Est. value
NOK 220,000

Financial health · 2025

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

Who owns SAMEIET KROSSNES?

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

Frequently asked questions about SAMEIET KROSSNES

What is the revenue of SAMEIET KROSSNES?

SAMEIET KROSSNES had revenue of NOK 161,000 in 2025.

Where is SAMEIET KROSSNES based?

SAMEIET KROSSNES has its business address in Haugesund.

Property

Business address c/o Vestbo BBL avd. Haugesund Kirkegata 130, 5527 Haugesund
Cadastral unit 1106-40/602/0/0
Building Annen kontorbygning · 1 unit

277 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.