BIZTRAC BETA
COMPANY REGISTER PROFILE
989769308 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

KVITFJELLHYTTA NUF

Org. no. 989769308 Norwegian division of foreign business enterprise (NUF) Nittedal Active
Ownership graph ↗
Revenue 2025 NOK 91,000
Operating profit NOK 11,000
Equity NOK 542,000

KVITFJELLHYTTA NUF is registered as a norwegian division of foreign business enterprise in Nittedal, Akershus with organisation number 989769308. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The most recent filed accounts, for the 2025 financial year, show NOK 91,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 91,000
Operating profit
NOK 11,000
Equity
NOK 542,000
Est. value
NOK 405,000

Financial health · 2025

Liquidity
400.64
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 KVITFJELLHYTTA NUF?

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

Frequently asked questions about KVITFJELLHYTTA NUF

What is the revenue of KVITFJELLHYTTA NUF?

KVITFJELLHYTTA NUF had revenue of NOK 91,000 in 2025.

Where is KVITFJELLHYTTA NUF based?

KVITFJELLHYTTA NUF has its business address in Nittedal.

Property

Business address Solveien 1, 1482 Nittedal
Cadastral unit 3232-15/87/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

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