BIZTRAC BETA
Civil engineering activities

SIVILINGENIØR A HELSEM AS

Org. no. 938635250 Limited company (AS) Trondheim Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −77,000
Equity NOK 4.2m
Incorporated 1986
Share capital NOK 100,000

Signals

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

SIVILINGENIØR A HELSEM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 938635250. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1986. Registered share capital is NOK 100,000. The company's stated purpose is: “Investering i aksjer og annen virksomhet beslektet med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −77,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −77,000
Equity
NOK 4.2m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns SIVILINGENIØR A HELSEM AS?

ANDREAS HELSEM
SIVILINGENIØR A HELSEM AS
NOK 0 rev. · NOK −77,000 profit

SIVILINGENIØR A HELSEM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR A HELSEM AS

Who owns SIVILINGENIØR A HELSEM AS?

ANDREAS HELSEM is the largest registered owner, with 98.0%.

What is the revenue of SIVILINGENIØR A HELSEM AS?

SIVILINGENIØR A HELSEM AS had revenue of NOK 0 in 2025.

Who is the general manager of SIVILINGENIØR A HELSEM AS?

Arvid Helsem is registered as general manager of SIVILINGENIØR A HELSEM AS.

Where is SIVILINGENIØR A HELSEM AS based?

SIVILINGENIØR A HELSEM AS has its business address in Tiller.

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.