BIZTRAC BETA
Civil engineering activities

ING. EIRIK MILDE AS

Org. no. 985850372 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −184,000
Equity NOK 103,000
Incorporated 2003
Share capital NOK 100,000

Signals

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

ING. EIRIK MILDE AS is registered as a limited company in Bergen, Vestland with organisation number 985850372. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rådgivende ingeniørvirksomhet innen prosjektadministrasjon, byggelånskontroll, taksering av fast eiendom og annen tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −184,000
Equity
NOK 103,000
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.6%
Good
Equity as a share of total capital

Who owns ING. EIRIK MILDE AS?

EIRIK MILDE
ING. EIRIK MILDE AS
NOK 1.5m rev. · NOK −184,000 profit

ING. EIRIK MILDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ING. EIRIK MILDE AS

Who owns ING. EIRIK MILDE AS?

EIRIK MILDE is the largest registered owner, with 100.0%.

What is the revenue of ING. EIRIK MILDE AS?

ING. EIRIK MILDE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of ING. EIRIK MILDE AS?

Eirik Milde is registered as general manager of ING. EIRIK MILDE AS.

Where is ING. EIRIK MILDE AS based?

ING. EIRIK MILDE AS has its business address in Nesttun.

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.