BIZTRAC BETA
Civil engineering activities

INGENIØR EVENSEN AS

Org. no. 931405888 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 572,000
Equity NOK 85,000
Incorporated 2023
Share capital NOK 30,000

INGENIØR EVENSEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931405888. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulent og rådgivningstjenester innenfor bygg og anlegg samt undervisning i seiling og sjømannskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 572,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 572,000
Equity
NOK 85,000
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.4%
Weak
Equity as a share of total capital

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

Who owns INGENIØR EVENSEN AS?

ANDREAS EVENSEN
INGENIØR EVENSEN AS
NOK 2.7m rev. · NOK 572,000 profit

INGENIØR EVENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGENIØR EVENSEN AS

Who owns INGENIØR EVENSEN AS?

ANDREAS EVENSEN is the largest registered owner, with 100.0%.

What is the revenue of INGENIØR EVENSEN AS?

INGENIØR EVENSEN AS had revenue of NOK 2.7m in 2025.

Who is the general manager of INGENIØR EVENSEN AS?

Andreas Evensen is registered as general manager of INGENIØR EVENSEN AS.

Where is INGENIØR EVENSEN AS based?

INGENIØR EVENSEN AS has its business address in Gressvik.

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.