BIZTRAC BETA
Rental and operating of own or leased real estate

WILOG NEWCO AS

Org. no. 932453428 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.7m
Equity NOK 1.3bn
Incorporated 2023
Share capital NOK 134,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

WILOG NEWCO AS is registered as a limited company in Oslo, Oslo with organisation number 932453428. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 134,000, divided into 1337000000 shares. The company's stated purpose is: “Å drive med oppkjøp og forvaltning av næringseiendom, herunder deltakelse i andre selskap, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.7m
Equity
NOK 1.3bn
Est. value
NOK 1.2bn

Financial health · 2024

Liquidity
294.84
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.4%
Very good
Equity as a share of total capital

Who owns WILOG NEWCO AS?

NSF V NORWAY HOLDING 9 AS
WILOG NEWCO AS
NOK 0 rev. · NOK −1.7m profit

WILOG NEWCO AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does WILOG NEWCO AS own?

WILOG NEWCO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WILOG NEWCO AS

Who owns WILOG NEWCO AS?

NSF V NORWAY HOLDING 9 AS is the largest registered owner, with 60.0%.

What is the revenue of WILOG NEWCO AS?

WILOG NEWCO AS had revenue of NOK 0 in 2024.

Where is WILOG NEWCO AS based?

WILOG NEWCO 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.