BIZTRAC BETA
Growing of other non-perennial crops

KJENSLIMOEN AS

Org. no. 991477780 Limited company (AS) Vestby Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 751,000
Operating profit NOK −201,000
Equity NOK 2.6m
Incorporated 2007
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−201k kr).

KJENSLIMOEN AS is registered as a limited company in Vestby, Akershus with organisation number 991477780. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2007. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Landruksvirksomhet, samt alt hva dermed står i denne forbindelse, videre å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 751,000 in revenue and NOK −201,000 in operating profit.

Key figures · 2025

Revenue
NOK 751,000
Operating profit
NOK −201,000
Equity
NOK 2.6m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns KJENSLIMOEN AS?

SKRUE KAPITAL AS
KJENSLIMOEN AS
NOK 751,000 rev. · NOK −201,000 profit

KJENSLIMOEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJENSLIMOEN AS

Who owns KJENSLIMOEN AS?

SKRUE KAPITAL AS is the largest registered owner, with 50.0%.

What is the revenue of KJENSLIMOEN AS?

KJENSLIMOEN AS had revenue of NOK 751,000 in 2025.

Who is the general manager of KJENSLIMOEN AS?

Finn Olav Myhrer is registered as general manager of KJENSLIMOEN AS.

Where is KJENSLIMOEN AS based?

KJENSLIMOEN AS has its business address in Vestby.

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.