BIZTRAC BETA
COMPANY REGISTER PROFILE
928132668 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Unit trusts

VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3

Org. no. 928132668 Unit trusts (VPFO) Bærum Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −8.3m
Equity NOK 5.4bn
Incorporated 2021

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8,3 mill kr).

VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3 is registered as a unit trusts in Bærum, Akershus with organisation number 928132668. The business is classified under unit trusts (NACE 64.311). The company was incorporated in 2021.

Former names: STOREBRAND GLOBAL OBLIGASJON 1-3 VERDIPAPIRFONDET

Key figures · 2025

Operating profit
NOK −8.3m
Equity
NOK 5.4bn
Est. value
NOK 3.9bn

Financial health · 2025

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

Who owns VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3?

No shareholders are registered for VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3

Where is VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3 based?

VERDIPAPIRFONDET STOREBRAND GLOBAL OBLIGASJON 1-3 has its business address in Lysaker.

Property

Business address Professor Kohts vei 9, 1366 Lysaker
Cadastral unit 3201-40/106/0/0

146 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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