BIZTRAC BETA
Site preparation

KN MASKINDRIFT & VAKTMESTERTJENESTER AS

Org. no. 930276235 Limited company (AS) Åsnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 111,000
Equity NOK 90,000
Incorporated 2022
Share capital NOK 30,000

KN MASKINDRIFT & VAKTMESTERTJENESTER AS is registered as a limited company in Åsnes, Innlandet with organisation number 930276235. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Anleggsvirksomhet med maskiner, vaktmestertjenester og andre produkter/ tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 111,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 111,000
Equity
NOK 90,000
Est. value
NOK 415,000

Financial health · 2024

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

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

Who owns KN MASKINDRIFT & VAKTMESTERTJENESTER AS?

KJETIL NORDBY
KN MASKINDRIFT & VAKTMESTERTJENESTER AS
NOK 4.4m rev. · NOK 111,000 profit

KN MASKINDRIFT & VAKTMESTERTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KN MASKINDRIFT & VAKTMESTERTJENESTER AS

Who owns KN MASKINDRIFT & VAKTMESTERTJENESTER AS?

KJETIL NORDBY is the largest registered owner, with 100.0%.

What is the revenue of KN MASKINDRIFT & VAKTMESTERTJENESTER AS?

KN MASKINDRIFT & VAKTMESTERTJENESTER AS had revenue of NOK 4.4m in 2024.

Where is KN MASKINDRIFT & VAKTMESTERTJENESTER AS based?

KN MASKINDRIFT & VAKTMESTERTJENESTER AS has its business address in Arneberg.

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.