biztrac. BETA
COMPANY REGISTER PROFILE
911916959 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

SIVILINGENIØR OWRENN AS

Org. no. 911916959 Limited company (AS) Elverum Incorporated 1975 Active
Operating profit NOK −24,000
Equity NOK 2.9m
Incorporated 1975
Share capital NOK 105,000

Signals

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

SIVILINGENIØR OWRENN AS is registered as a limited company in Elverum, Innlandet with organisation number 911916959. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1975. Registered share capital is NOK 105,000, divided into 1 shares. The company's stated purpose is: “Drive prosjektstyring, bygge- og anleggsledelse samt kurs- og rådgivningstjeneste innenfor BA-næringen, investering i utstyr og eiendom samt aksjetegning eller på annen måte gjøre seg interessert i andre aktiviteter innen bransjen.”.

Former names: JOHN GALTEN AS, JOHN GALTEN EIENDOM AS

Key figures · 2025

Operating profit
NOK −24,000
▲ +18 %
Equity
NOK 2.9m
▼ −15 %
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns SIVILINGENIØR OWRENN AS?

SIVILINGENIØR OWRENN AS
· NOK −24,000 profit

SIVILINGENIØR OWRENN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIVILINGENIØR OWRENN AS own?

SIVILINGENIØR OWRENN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIVILINGENIØR OWRENN AS

Who owns SIVILINGENIØR OWRENN AS?

Ulf Erik Owrenn is the largest registered owner, with 100.0%.

Where is SIVILINGENIØR OWRENN AS based?

SIVILINGENIØR OWRENN AS has its business address in Elverum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.