BIZTRAC BETA
Rental and operating of own or leased real estate

KIIL MASKIN & UTLEIE AS

Org. no. 962103138 Limited company (AS) Målselv Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 48,000
Equity NOK 1.9m
Incorporated 1991
Share capital NOK 200,000

KIIL MASKIN & UTLEIE AS is registered as a limited company in Målselv, Troms with organisation number 962103138. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 200,000. The company's stated purpose is: “Å tilby tjenester med maskiner og utstyr, samt utleie av maskiner og utstyr. Videre skal selskapet kunne delta i annen virk- somhet med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 48,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 48,000
Equity
NOK 1.9m
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.8%
Very good
Equity as a share of total capital

Who owns KIIL MASKIN & UTLEIE AS?

STIG TERJE KIIL
KIIL MASKIN & UTLEIE AS
NOK 2.2m rev. · NOK 48,000 profit

KIIL MASKIN & UTLEIE AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIIL MASKIN & UTLEIE AS

Who owns KIIL MASKIN & UTLEIE AS?

STIG TERJE KIIL is the largest registered owner, with 20.0%.

What is the revenue of KIIL MASKIN & UTLEIE AS?

KIIL MASKIN & UTLEIE AS had revenue of NOK 2.2m in 2024.

Who is the general manager of KIIL MASKIN & UTLEIE AS?

Stig Terje Kiil is registered as general manager of KIIL MASKIN & UTLEIE AS.

Where is KIIL MASKIN & UTLEIE AS based?

KIIL MASKIN & UTLEIE AS has its business address in Bardufoss.

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.