BIZTRAC BETA
Rental and operating of own or leased real estate

REQ INFRAHEIM HOLDING AS

Org. no. 934389921 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 1.4m

Signals

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

REQ INFRAHEIM HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 934389921. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 1.4m, divided into 1402000 shares. The company's stated purpose is: “Å kjøpe, eie, forvalte, drifte, utvikle og drive utleie av fast eiendom, eller selskaper som direkte eller indirekte oppfyller slikt formål, samt annen virksomhet som har sammenheng med dette.”.

Key figures · 2024

Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns REQ INFRAHEIM HOLDING AS?

REQ REAL ESTATE FUND II AS
REQ INFRAHEIM HOLDING AS
· NOK 0 profit

REQ INFRAHEIM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REQ INFRAHEIM HOLDING AS own?

REQ INFRAHEIM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REQ INFRAHEIM HOLDING AS

Who owns REQ INFRAHEIM HOLDING AS?

REQ REAL ESTATE FUND II AS is the largest registered owner, with 100.0%.

Where is REQ INFRAHEIM HOLDING AS based?

REQ INFRAHEIM HOLDING 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.