BIZTRAC BETA
Rental and leasing of agricultural machinery and equipment

KJENÅS ENTREPRENØR AS

Org. no. 998419417 Limited company (AS) Flesberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 136,000
Equity NOK 1.4m
Incorporated 2012
Share capital NOK 100,000

KJENÅS ENTREPRENØR AS is registered as a limited company in Flesberg, Buskerud with organisation number 998419417. The business is classified under rental and leasing of agricultural machinery and equipment (NACE 77.310). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive entreprenørvirksomhet, utleie av maskiner, handel, deltakelse i andre selskap og alt hva derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 136,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 136,000
Equity
NOK 1.4m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns KJENÅS ENTREPRENØR AS?

ROGER KJENÅS INVEST AS
KJENÅS ENTREPRENØR AS
NOK 4.6m rev. · NOK 136,000 profit

KJENÅS ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJENÅS ENTREPRENØR AS

Who owns KJENÅS ENTREPRENØR AS?

ROGER KJENÅS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KJENÅS ENTREPRENØR AS?

KJENÅS ENTREPRENØR AS had revenue of NOK 4.6m in 2024.

Who is the general manager of KJENÅS ENTREPRENØR AS?

Roger Kjenås is registered as general manager of KJENÅS ENTREPRENØR AS.

Where is KJENÅS ENTREPRENØR AS based?

KJENÅS ENTREPRENØR AS has its business address in Kongsberg.

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.