BIZTRAC BETA
Repair and maintenance of machinery

LJLAURITZEN AS

Org. no. 936128165 Limited company (AS) Halden Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 178,000
Operating profit NOK 172,000
Equity NOK 195,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-08-23.

LJLAURITZEN AS is registered as a limited company in Halden, Østfold with organisation number 936128165. 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 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen reparasjon av maskiner og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 178,000 in revenue and NOK 172,000 in operating profit.

Key figures · 2025

Revenue
NOK 178,000
Operating profit
NOK 172,000
Equity
NOK 195,000
Est. value
NOK 656,000

Financial health · 2025

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

Who owns LJLAURITZEN AS?

JOHAN LAURITZEN AS
LJLAURITZEN AS
NOK 178,000 rev. · NOK 172,000 profit

LJLAURITZEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LJLAURITZEN AS

Who owns LJLAURITZEN AS?

JOHAN LAURITZEN AS is the largest registered owner, with 100.0%.

What is the revenue of LJLAURITZEN AS?

LJLAURITZEN AS had revenue of NOK 178,000 in 2025.

Who is the general manager of LJLAURITZEN AS?

Leif Johan Lauritzen is registered as general manager of LJLAURITZEN AS.

Where is LJLAURITZEN AS based?

LJLAURITZEN AS has its business address in Halden.

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.