BIZTRAC BETA
Construction of residential and non-residential buildings

TØMRER LEON A. KLEIVA AS

Org. no. 813186462 Limited company (AS) Froland Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 42,000
Equity NOK 432,000
Incorporated 2014
Share capital NOK 100,000

TØMRER LEON A. KLEIVA AS is registered as a limited company in Froland, Agder with organisation number 813186462. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Levering av tømrertjenester og annet som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 42,000
Equity
NOK 432,000
Est. value
NOK 333,000

Financial health · 2025

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

Who owns TØMRER LEON A. KLEIVA AS?

LEON ARNE ÅMLID KLEIVA
TØMRER LEON A. KLEIVA AS
NOK 2.9m rev. · NOK 42,000 profit

TØMRER LEON A. KLEIVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRER LEON A. KLEIVA AS

Who owns TØMRER LEON A. KLEIVA AS?

LEON ARNE ÅMLID KLEIVA is the largest registered owner, with 100.0%.

What is the revenue of TØMRER LEON A. KLEIVA AS?

TØMRER LEON A. KLEIVA AS had revenue of NOK 2.9m in 2025.

Who is the general manager of TØMRER LEON A. KLEIVA AS?

Leon Arne Åmlid Kleiva is registered as general manager of TØMRER LEON A. KLEIVA AS.

Where is TØMRER LEON A. KLEIVA AS based?

TØMRER LEON A. KLEIVA AS has its business address in Mjåvatn.

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.