BIZTRAC BETA
Support activities for crop production

SØRLI MASKINLAG AS

Org. no. 926328980 Limited company (AS) Lillestrøm Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 194,000
Operating profit NOK −11,000
Equity NOK 4,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SØRLI MASKINLAG AS is registered as a limited company in Lillestrøm, Akershus with organisation number 926328980. The business is classified under support activities for crop production (NACE 01.610). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 120 shares. The company's stated purpose is: “Yte tjenester med egne driftsmidler innenfor landbruksektoren, herunder å delta i andre foretak innenfor landbruksektoren samt andre oppgaver som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 194,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 194,000
Operating profit
NOK −11,000
Equity
NOK 4,000
Est. value
NOK 111,000

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SØRLI MASKINLAG AS?

ODD HOFSKELRUD
SØRLI MASKINLAG AS
NOK 194,000 rev. · NOK −11,000 profit

SØRLI MASKINLAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRLI MASKINLAG AS

Who owns SØRLI MASKINLAG AS?

ODD HOFSKELRUD is the largest registered owner, with 33.3%.

What is the revenue of SØRLI MASKINLAG AS?

SØRLI MASKINLAG AS had revenue of NOK 194,000 in 2025.

Where is SØRLI MASKINLAG AS based?

SØRLI MASKINLAG AS has its business address in Sørum.

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.