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

SAMEIET LIABYGGET

Org. no. 930883182 Condominium flat owner (ESEK) Skien Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 524,000
Operating profit NOK 238,000
Incorporated 2005

SAMEIET LIABYGGET is registered as a condominium flat owner in Skien, Telemark with organisation number 930883182. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2005. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 524,000 in revenue and NOK 238,000 in operating profit.

Key figures · 2025

Revenue
NOK 524,000
Operating profit
NOK 238,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns SAMEIET LIABYGGET?

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

Frequently asked questions about SAMEIET LIABYGGET

What is the revenue of SAMEIET LIABYGGET?

SAMEIET LIABYGGET had revenue of NOK 524,000 in 2025.

Where is SAMEIET LIABYGGET based?

SAMEIET LIABYGGET has its business address in Skien.

Property

Business address c/o Skien Boligbyggelag Cappelens gate 11, 3717 Skien
Cadastral unit 4003-300/682/0/0

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