BIZTRAC BETA
Construction of residential and non-residential buildings

KILE HÅNDLAFT AS

Org. no. 989249002 Limited company (AS) Fyresdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 10.7m
Operating profit NOK 566,000
Equity NOK 2.2m
Incorporated 2005
Employees 6
Share capital NOK 96,000

KILE HÅNDLAFT AS is registered as a limited company in Fyresdal, Telemark with organisation number 989249002. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005 and has 6 registered employees. Registered share capital is NOK 96,000, divided into 300 shares. The company's stated purpose is: “Tømrervirksomhet samt kjøp og salg av varer og tjenester som naturlig knytter seg til denne virksomheten.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.7m in revenue and NOK 566,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.7m
Operating profit
NOK 566,000
Equity
NOK 2.2m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns KILE HÅNDLAFT AS?

KNUT OLAV KILE
KILE HÅNDLAFT AS
NOK 10.7m rev. · NOK 566,000 profit

KILE HÅNDLAFT AS has 3 registered shareholders:

All shareholders and roles →

Group structure

KILE HÅNDLAFT AS er morselskap for 1 datterselskap:

Frequently asked questions about KILE HÅNDLAFT AS

Who owns KILE HÅNDLAFT AS?

KNUT OLAV KILE is the largest registered owner, with 33.3%.

What is the revenue of KILE HÅNDLAFT AS?

KILE HÅNDLAFT AS had revenue of NOK 10.7m in 2025.

Who is the general manager of KILE HÅNDLAFT AS?

Jørgen Kile is registered as general manager of KILE HÅNDLAFT AS.

Where is KILE HÅNDLAFT AS based?

KILE HÅNDLAFT AS has its business address in Fyresdal.

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.