BIZTRAC BETA
Construction of residential and non-residential buildings

E & E BYGG AS

Org. no. 931945505 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 63,000
Operating profit NOK 9,000
Equity NOK 91,000
Incorporated 2023
Share capital NOK 30,000

E & E BYGG AS is registered as a limited company in Asker, Akershus with organisation number 931945505. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 63,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 63,000
Operating profit
NOK 9,000
Equity
NOK 91,000
Est. value
NOK 68,000

Financial health · 2025

Liquidity
2.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.6%
Weak
Equity as a share of total capital

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

Who owns E & E BYGG AS?

ERTZGAARD BYGG AS
E & E BYGG AS
NOK 63,000 rev. · NOK 9,000 profit

E & E BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about E & E BYGG AS

Who owns E & E BYGG AS?

ERTZGAARD BYGG AS is the largest registered owner, with 50.0%.

What is the revenue of E & E BYGG AS?

E & E BYGG AS had revenue of NOK 63,000 in 2025.

Who is the general manager of E & E BYGG AS?

Jørgen Eriksen Ertzgaard is registered as general manager of E & E BYGG AS.

Where is E & E BYGG AS based?

E & E BYGG AS has its business address in Røyken.

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.