BIZTRAC BETA
Civil engineering activities

SIVILINGENIØR SAM LORGEN AS

Org. no. 913990617 Limited company (AS) Ålesund Incorporated 1975 Active
Ownership graph ↗
Revenue 2025 NOK 408,000
Operating profit NOK 335,000
Equity NOK 1.1m
Incorporated 1975
Share capital NOK 100,000

SIVILINGENIØR SAM LORGEN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 913990617. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1975. Registered share capital is NOK 100,000. The company's stated purpose is: “Rådgivende ingeniørvirksomhet i bygge- og anleggs- bransjen og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 408,000 in revenue and NOK 335,000 in operating profit.

Key figures · 2025

Revenue
NOK 408,000
Operating profit
NOK 335,000
Equity
NOK 1.1m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns SIVILINGENIØR SAM LORGEN AS?

SVERRE LORGEN
SIVILINGENIØR SAM LORGEN AS
NOK 408,000 rev. · NOK 335,000 profit

SIVILINGENIØR SAM LORGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR SAM LORGEN AS

Who owns SIVILINGENIØR SAM LORGEN AS?

SVERRE LORGEN is the largest registered owner, with 100.0%.

What is the revenue of SIVILINGENIØR SAM LORGEN AS?

SIVILINGENIØR SAM LORGEN AS had revenue of NOK 408,000 in 2025.

Who is the general manager of SIVILINGENIØR SAM LORGEN AS?

Sverre Lorgen is registered as general manager of SIVILINGENIØR SAM LORGEN AS.

Where is SIVILINGENIØR SAM LORGEN AS based?

SIVILINGENIØR SAM LORGEN AS has its business address in Ålesund.

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.