BIZTRAC BETA
Rental and operating of own or leased real estate

BOLIGBYGGERN SELBU AS

Org. no. 920844537 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 793,000
Operating profit NOK 416,000
Equity NOK 60,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOLIGBYGGERN SELBU AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920844537. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utleie, forvaltning og salg av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 793,000 in revenue and NOK 416,000 in operating profit.

Key figures · 2024

Revenue
NOK 793,000
Operating profit
NOK 416,000
Equity
NOK 60,000
Est. value
NOK 502,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.7%
Weak
Equity as a share of total capital

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

Who owns BOLIGBYGGERN SELBU AS?

LOFT EIENDOM AS
BOLIGBYGGERN SELBU AS
NOK 793,000 rev. · NOK 416,000 profit

BOLIGBYGGERN SELBU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGBYGGERN SELBU AS

Who owns BOLIGBYGGERN SELBU AS?

LOFT EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BOLIGBYGGERN SELBU AS?

BOLIGBYGGERN SELBU AS had revenue of NOK 793,000 in 2024.

Where is BOLIGBYGGERN SELBU AS based?

BOLIGBYGGERN SELBU AS has its business address in Ranheim.

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.