BIZTRAC BETA
General cleaning of buildings

HØYT NIVÅ HARSTAD AS

Org. no. 926474375 Limited company (AS) Harstad Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 286,000
Equity NOK 1,000
Incorporated 2021
Employees 6
Share capital NOK 30,000

HØYT NIVÅ HARSTAD AS is registered as a limited company in Harstad, Troms with organisation number 926474375. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rengjøringsvirksomhet - daglig rengjøring, trappevask, vinduspuss, fasadevask og takvask. Liftarbeid. Vaktmestertjenester. Rehabiltitering, byggtjenester, byggearbeider ol. Samt andre tjenester som faller naturlig inn.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 286,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 286,000
Equity
NOK 1,000
Est. value
NOK 1.2m

Financial health · 2025

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

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

Who owns HØYT NIVÅ HARSTAD AS?

LARS CHRISTOFFER FJELLTVEIT
HØYT NIVÅ HARSTAD AS
NOK 3.5m rev. · NOK 286,000 profit

HØYT NIVÅ HARSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØYT NIVÅ HARSTAD AS

Who owns HØYT NIVÅ HARSTAD AS?

LARS CHRISTOFFER FJELLTVEIT is the largest registered owner, with 100.0%.

What is the revenue of HØYT NIVÅ HARSTAD AS?

HØYT NIVÅ HARSTAD AS had revenue of NOK 3.5m in 2025.

Where is HØYT NIVÅ HARSTAD AS based?

HØYT NIVÅ HARSTAD AS has its business address in Harstad.

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.