BIZTRAC BETA
Repair and maintenance of machinery

LORENTZEN-SERVICE AS

Org. no. 935719356 Limited company (AS) Vennesla Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 1.3m
Equity NOK 68,000
Incorporated 2025
Share capital NOK 30,000

LORENTZEN-SERVICE AS is registered as a limited company in Vennesla, Agder with organisation number 935719356. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Reparasjon av maskiner til landbruk/skogbruk, bygg- og anlegg og industri ellers. Lastebiltransport.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 1.3m
Equity
NOK 68,000
Est. value
NOK 4.1m

Financial health · 2025

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

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

Who owns LORENTZEN-SERVICE AS?

SEBASTIAN LORENTZEN
LORENTZEN-SERVICE AS
NOK 1.6m rev. · NOK 1.3m profit

LORENTZEN-SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LORENTZEN-SERVICE AS

Who owns LORENTZEN-SERVICE AS?

SEBASTIAN LORENTZEN is the largest registered owner, with 100.0%.

What is the revenue of LORENTZEN-SERVICE AS?

LORENTZEN-SERVICE AS had revenue of NOK 1.6m in 2025.

Who is the general manager of LORENTZEN-SERVICE AS?

Sebastian Lorentzen is registered as general manager of LORENTZEN-SERVICE AS.

Where is LORENTZEN-SERVICE AS based?

LORENTZEN-SERVICE AS has its business address in Vennesla.

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.