biztrac. BETA
COMPANY REGISTER PROFILE
928129152 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

INDRE BOLIG AS

Org. no. 928129152 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 163,000
Incorporated 2021
Share capital NOK 99,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

INDRE BOLIG AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928129152. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 99,000, divided into 99 shares. The company's stated purpose is: “Investeringer i ulike aktiva herunder, men ikke begrenset til, eiendomsinvesteringer/-utvikling, verdipapirer, fond m.v., og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
▼ −20 %
Equity
NOK 163,000
▼ −0 %
Est. value
NOK 534,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns INDRE BOLIG AS?

INDRE BOLIG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INDRE BOLIG AS

Who owns INDRE BOLIG AS?

ATP INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of INDRE BOLIG AS?

INDRE BOLIG AS had revenue of NOK 0 in 2025.

Where is INDRE BOLIG AS based?

INDRE BOLIG AS has its business address in Lillestrøm.

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.