BIZTRAC BETA
Repair and maintenance of motor vehicles

KJEVERUD BILLAKKERING AS

Org. no. 919212101 Limited company (AS) Stange Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 93,000
Equity NOK 98,000
Incorporated 2017
Share capital NOK 30,000

KJEVERUD BILLAKKERING AS is registered as a limited company in Stange, Innlandet with organisation number 919212101. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppretting og lakkering av biler. Kjøp og salg av bruktbiler og deler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 93,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 93,000
Equity
NOK 98,000
Est. value
NOK 293,000

Financial health · 2024

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

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

Who owns KJEVERUD BILLAKKERING AS?

KNUT DAGFINN KJEVERUD
KJEVERUD BILLAKKERING AS
NOK 1.4m rev. · NOK 93,000 profit

KJEVERUD BILLAKKERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJEVERUD BILLAKKERING AS

Who owns KJEVERUD BILLAKKERING AS?

KNUT DAGFINN KJEVERUD is the largest registered owner, with 100.0%.

What is the revenue of KJEVERUD BILLAKKERING AS?

KJEVERUD BILLAKKERING AS had revenue of NOK 1.4m in 2024.

Who is the general manager of KJEVERUD BILLAKKERING AS?

Knut Dagfinn Kjeverud is registered as general manager of KJEVERUD BILLAKKERING AS.

Where is KJEVERUD BILLAKKERING AS based?

KJEVERUD BILLAKKERING AS has its business address in Åsvang.

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.