biztrac. BETA
COMPANY REGISTER PROFILE
994382365 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other food

NORDIC VISIONS NUF

Org. no. 994382365 Norwegian division of foreign business enterprise (NUF) Bærum Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −144,000
Equity NOK −11,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−144k kr).

NORDIC VISIONS NUF is registered as a norwegian division of foreign business enterprise in Bærum, Akershus with organisation number 994382365. The business is classified under retail sale of other food (NACE 47.270). The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −144,000 in operating profit.

Former names: NORDIC VISIONS, GULLBAGEN.NO

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −144,000
Equity
NOK −11,000
▼ −105 %

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
-76.8%
Not satisfactory
Return on total assets
Solidity
-21.1%
Weak
Equity as a share of total capital

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

Who owns NORDIC VISIONS NUF?

No shareholders are registered for NORDIC VISIONS NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does NORDIC VISIONS NUF own?

NORDIC VISIONS NUF holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORDIC VISIONS NUF

What is the revenue of NORDIC VISIONS NUF?

NORDIC VISIONS NUF had revenue of NOK 0 in 2025.

Who is the general manager of NORDIC VISIONS NUF?

Andreas Norem is registered as general manager of NORDIC VISIONS NUF.

Where is NORDIC VISIONS NUF based?

NORDIC VISIONS NUF has its business address in Høvik.

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.