BIZTRAC BETA
Buying and selling of own real estate

IN BOLIG AS

Org. no. 924304871 Limited company (AS) Ringsaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 231,000
Operating profit NOK −923,000
Equity NOK −1.6m
Incorporated 2019
Share capital NOK 900,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−923k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

IN BOLIG AS is registered as a limited company in Ringsaker, Innlandet with organisation number 924304871. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 900,000, divided into 9000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, og alt som er nærliggende til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 231,000 in revenue and NOK −923,000 in operating profit.

Key figures · 2024

Revenue
NOK 231,000
Operating profit
NOK −923,000
Equity
NOK −1.6m

Financial health · 2024

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.3%
Weak
Equity as a share of total capital

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

Who owns IN BOLIG AS?

RAFOS HOLDING AS
IN BOLIG AS
NOK 231,000 rev. · NOK −923,000 profit

IN BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about IN BOLIG AS

Who owns IN BOLIG AS?

RAFOS HOLDING AS is the largest registered owner, with 99.0%.

What is the revenue of IN BOLIG AS?

IN BOLIG AS had revenue of NOK 231,000 in 2024.

Where is IN BOLIG AS based?

IN BOLIG AS has its business address in Brumunddal.

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.