BIZTRAC BETA
Other building completion and finishing

LILLELAND AS

Org. no. 893112812 Limited company (AS) Klepp Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 52.1m
Operating profit NOK 11.7m
Equity NOK 7.9m
Incorporated 2008
Employees 21
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LILLELAND AS is registered as a limited company in Klepp, Rogaland with organisation number 893112812. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2008 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet innen passiv brannsikring, byggmestervirksomhet, samt handel og agenturer av varer innen disse bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 52.1m in revenue and NOK 11.7m in operating profit.

Key figures · 2024

Revenue
NOK 52.1m
Operating profit
NOK 11.7m
Equity
NOK 7.9m
Est. value
NOK 36.6m

Financial health · 2024

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns LILLELAND AS?

JKM AS
LILLELAND AS
NOK 52.1m rev. · NOK 11.7m profit

LILLELAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLELAND AS

Who owns LILLELAND AS?

JKM AS is the largest registered owner, with 100.0%.

What is the revenue of LILLELAND AS?

LILLELAND AS had revenue of NOK 52.1m in 2024.

Who is the general manager of LILLELAND AS?

Jane Kristine Lilleland is registered as general manager of LILLELAND AS.

Where is LILLELAND AS based?

LILLELAND AS has its business address in Kleppe.

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.