BIZTRAC BETA
COMPANY REGISTER PROFILE
986179399 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other business support service activities n.e.c.

KOLCON NUF

Org. no. 986179399 Norwegian division of foreign business enterprise (NUF) Sola Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −399

Signals

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

KOLCON NUF is registered as a norwegian division of foreign business enterprise in Sola, Rogaland with organisation number 986179399. The business is classified under other business support service activities n.e.c. (NACE 82.990). The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −399 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −399

Financial health · 2025

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

Who owns KOLCON NUF?

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

Frequently asked questions about KOLCON NUF

What is the revenue of KOLCON NUF?

KOLCON NUF had revenue of NOK 0 in 2025.

Who is the general manager of KOLCON NUF?

Steinar Vigdel Kolnes is registered as general manager of KOLCON NUF.

Where is KOLCON NUF based?

KOLCON NUF has its business address in Sola.

Property

Business address Sør Kolnesvegen 78, 4055 Sola
Cadastral unit 1124-13/16/0/0
Building Enebolig · 1 unit

6 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.