BIZTRAC BETA
Computer programming activities

ENGHOUSE NETWORKS (NORWAY) AS

Org. no. 814736962 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 15.7m
Operating profit NOK 8.0m
Equity NOK 518,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-13 Adresseendring registrert 2026-05-13.

ENGHOUSE NETWORKS (NORWAY) AS is registered as a limited company in Bærum, Akershus with organisation number 814736962. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling og salg av programvare, konsulentvirksomhet, forvaltning av eierinteresser og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.7m in revenue and NOK 8.0m in operating profit.

Key figures · 2025

Revenue
NOK 15.7m
Operating profit
NOK 8.0m
Equity
NOK 518,000
Est. value
NOK 26.5m

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

Who owns ENGHOUSE NETWORKS (NORWAY) AS?

LOCUS SOLUTIONS AS
ENGHOUSE NETWORKS (NORWAY) AS
NOK 15.7m rev. · NOK 8.0m profit

ENGHOUSE NETWORKS (NORWAY) AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGHOUSE NETWORKS (NORWAY) AS

Who owns ENGHOUSE NETWORKS (NORWAY) AS?

LOCUS SOLUTIONS AS is the largest registered owner, with 100.0%.

What is the revenue of ENGHOUSE NETWORKS (NORWAY) AS?

ENGHOUSE NETWORKS (NORWAY) AS had revenue of NOK 15.7m in 2025.

Where is ENGHOUSE NETWORKS (NORWAY) AS based?

ENGHOUSE NETWORKS (NORWAY) AS has its business address in Fornebu.

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.