BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

L-H SERVICE AS

Org. no. 924897058 Limited company (AS) Nord-Odal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 389,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 50,000

L-H SERVICE AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 924897058. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Kjøp og salg av maskiner og redskaper, vedlikeholds- og entreprenørtjenester innen maskin og landbruk, utleie av maskiner/utstyr og arbeidskraft, samt alt som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 389,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 389,000
Equity
NOK 1.1m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns L-H SERVICE AS?

OLE-CHRISTIAN GRANLI LØKKER
L-H SERVICE AS
NOK 3.7m rev. · NOK 389,000 profit

L-H SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about L-H SERVICE AS

Who owns L-H SERVICE AS?

OLE-CHRISTIAN GRANLI LØKKER is the largest registered owner, with 50.0%.

What is the revenue of L-H SERVICE AS?

L-H SERVICE AS had revenue of NOK 3.7m in 2025.

Who is the general manager of L-H SERVICE AS?

Ole-Christian Granli Løkker is registered as general manager of L-H SERVICE AS.

Where is L-H SERVICE AS based?

L-H SERVICE AS has its business address in Sagstua.

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.