biztrac. BETA
COMPANY REGISTER PROFILE
916876963 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of financing conduits

NREP INVESTCO 47 AS

Org. no. 916876963 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 21.9m
Incorporated 2016
Share capital NOK 851,000

Signals

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

NREP INVESTCO 47 AS is registered as a limited company in Oslo, Oslo with organisation number 916876963. The business is classified under activities of financing conduits (NACE 64.220). The company was incorporated in 2016. Registered share capital is NOK 851,000, divided into 2837703 shares. The company's stated purpose is: “Investering i selskaper og fond, og alt annet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −60,000
▲ +47 %
Equity
NOK 21.9m
▲ +1 %
Est. value
NOK 13.0m

Financial health · 2025

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

Who owns NREP INVESTCO 47 AS?

GO4G REAL ESTATE OPPORTUNITY, LLC US
HANS RYE HOLDING APS DK
SAL HOLDING AS DK
KIDCO APS DK
NREP INVESTCO 47 AS
· NOK −60,000 profit

NREP INVESTCO 47 AS has 4 registered shareholders:

  • GO4G REAL ESTATE OPPORTUNITY, LLC 34.2%
  • HANS RYE HOLDING APS 29.3%
  • SAL HOLDING AS 26.4%
  • KIDCO APS 10.2%
All shareholders and roles →

Frequently asked questions about NREP INVESTCO 47 AS

Who owns NREP INVESTCO 47 AS?

GO4G REAL ESTATE OPPORTUNITY, LLC is the largest registered owner, with 34.2%.

Who is the general manager of NREP INVESTCO 47 AS?

Jens Petter Hagen is registered as general manager of NREP INVESTCO 47 AS.

Where is NREP INVESTCO 47 AS based?

NREP INVESTCO 47 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.