BIZTRAC BETA
Rental and operating of own or leased real estate

BOLIGBY AS

Org. no. 928344843 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK −177,000
Equity NOK −214,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−214k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−177k kr).

BOLIGBY AS is registered as a limited company in Oslo, Oslo with organisation number 928344843. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å erverve, eie og selge aksjer samt forvalte avkastning av disse. Erverve, drifte og selge eiendommer, drive rådgivning og tjenesteyting for andre virksomheter, deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK −177,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK −177,000
Equity
NOK −214,000

Financial health · 2025

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

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

Who owns BOLIGBY AS?

FIRK INVEST AS
BOLIGBY AS
NOK 3.4m rev. · NOK −177,000 profit

BOLIGBY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOLIGBY AS

Who owns BOLIGBY AS?

FIRK INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BOLIGBY AS?

BOLIGBY AS had revenue of NOK 3.4m in 2025.

Where is BOLIGBY AS based?

BOLIGBY AS has its business address in Oslo.

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.