BIZTRAC BETA
Repair and maintenance of machinery

LIFLAND AGRI AS

Org. no. 927761912 Limited company (AS) Hamar Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 54.5m
Operating profit NOK 1.6m
Equity NOK 7.0m
Incorporated 2021
Employees 22
Share capital NOK 4.6m

LIFLAND AGRI AS is registered as a limited company in Hamar, Innlandet with organisation number 927761912. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021 and has 22 registered employees. Registered share capital is NOK 4.6m, divided into 73164 shares. The company's stated purpose is: “Salg og service til landbruksbransjen, og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 54.5m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 54.5m
Operating profit
NOK 1.6m
Equity
NOK 7.0m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns LIFLAND AGRI AS?

LIFLAND HOLDING AS
LIFLAND AGRI AS
NOK 54.5m rev. · NOK 1.6m profit

LIFLAND AGRI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIFLAND AGRI AS own?

LIFLAND AGRI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIFLAND AGRI AS

Who owns LIFLAND AGRI AS?

LIFLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIFLAND AGRI AS?

LIFLAND AGRI AS had revenue of NOK 54.5m in 2024.

Who is the general manager of LIFLAND AGRI AS?

Jon Kristian Flesvik is registered as general manager of LIFLAND AGRI AS.

Where is LIFLAND AGRI AS based?

LIFLAND AGRI AS has its business address in Hamar.

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.