BIZTRAC BETA
Rental and operating of own or leased real estate

REDE BOLIG AS

Org. no. 928624676 Limited company (AS) Rælingen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK 45,000
Equity NOK −454,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−454k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

REDE BOLIG AS is registered as a limited company in Rælingen, Akershus with organisation number 928624676. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte, utvikle, bygge, selge og utleie av eiendommer, både bolig og næring.”. The most recent filed accounts, for the 2024 financial year, show NOK 156,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK 45,000
Equity
NOK −454,000
Est. value
NOK 309,000

Financial health · 2024

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

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

Who owns REDE BOLIG AS?

HOLTENGRUPPEN AS
REDE BOLIG AS
NOK 156,000 rev. · NOK 45,000 profit

REDE BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REDE BOLIG AS

Who owns REDE BOLIG AS?

HOLTENGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of REDE BOLIG AS?

REDE BOLIG AS had revenue of NOK 156,000 in 2024.

Where is REDE BOLIG AS based?

REDE BOLIG AS has its business address in Nordby.

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.