BIZTRAC BETA
Development of building projects

ENG HOLDING AS

Org. no. 977176107 Limited company (AS) Våler Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 594,000
Operating profit NOK 277,000
Equity NOK −2.0m
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,0 mill kr).

ENG HOLDING AS is registered as a limited company in Våler, Østfold with organisation number 977176107. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og utleie av løsøre og fast eiendom samt forestå investering i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 594,000 in revenue and NOK 277,000 in operating profit.

Key figures · 2024

Revenue
NOK 594,000
Operating profit
NOK 277,000
Equity
NOK −2.0m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-150.1%
Weak
Equity as a share of total capital

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

Who owns ENG HOLDING AS?

OLE ROBERT FIMBUL-KISERUD
ENG HOLDING AS
NOK 594,000 rev. · NOK 277,000 profit

ENG HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ENG HOLDING AS own?

ENG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENG HOLDING AS

Who owns ENG HOLDING AS?

OLE ROBERT FIMBUL-KISERUD is the largest registered owner, with 40.0%.

What is the revenue of ENG HOLDING AS?

ENG HOLDING AS had revenue of NOK 594,000 in 2024.

Where is ENG HOLDING AS based?

ENG HOLDING AS has its business address in Sperrebotn.

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.