biztrac. BETA
COMPANY REGISTER PROFILE
921862164 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠BOLIGOPP AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Construction of residential and non-residential buildings

BOLIGOPP AS

Org. no. 921862164 Limited company (AS) Trondheim Incorporated 2018 In liquidation
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 178,000
Equity NOK 78,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

BOLIGOPP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921862164. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 178,000 in operating profit.

Former names: CAPITAL BYGG AS

Key figures · 2025

Revenue
NOK 1.1m
▲ +151 %
Operating profit
NOK 178,000
▲ +140 %
Equity
NOK 78,000
▲ +197 %

Financial health · 2025

Liquidity
2.30
Very good
Current assets ÷ current liabilities
Profitability
74.0%
Very good
Return on total assets
Solidity
56.5%
Weak
Equity as a share of total capital

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

Who owns BOLIGOPP AS?

BOLIGOPP AS
NOK 1.1m rev. · NOK 178,000 profit

BOLIGOPP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGOPP AS

Who owns BOLIGOPP AS?

Petter Swierk is the largest registered owner, with 100.0%.

What is the revenue of BOLIGOPP AS?

BOLIGOPP AS had revenue of NOK 1.1m in 2025.

Where is BOLIGOPP AS based?

BOLIGOPP AS has its business address in Trondheim.

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

Report a problem

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