BIZTRAC BETA
Buying and selling of own real estate

OPTIMAL BYGG & EIENDOM AS

Org. no. 984806574 Limited company (AS) Nittedal Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 120,000
Equity NOK 767,000
Incorporated 2002
Share capital NOK 500,000

OPTIMAL BYGG & EIENDOM AS is registered as a limited company in Nittedal, Akershus with organisation number 984806574. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2002. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eiendomsutvikling, herunder kjøp av tomt, prosjektering, bygging og salg av bolig samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 120,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 120,000
Equity
NOK 767,000
Est. value
NOK 841,000

Financial health · 2024

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

Who owns OPTIMAL BYGG & EIENDOM AS?

JOHNNY ENGER
OPTIMAL BYGG & EIENDOM AS
NOK 3.1m rev. · NOK 120,000 profit

OPTIMAL BYGG & EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPTIMAL BYGG & EIENDOM AS

Who owns OPTIMAL BYGG & EIENDOM AS?

JOHNNY ENGER is the largest registered owner, with 100.0%.

What is the revenue of OPTIMAL BYGG & EIENDOM AS?

OPTIMAL BYGG & EIENDOM AS had revenue of NOK 3.1m in 2024.

Who is the general manager of OPTIMAL BYGG & EIENDOM AS?

Johnny Enger is registered as general manager of OPTIMAL BYGG & EIENDOM AS.

Where is OPTIMAL BYGG & EIENDOM AS based?

OPTIMAL BYGG & EIENDOM AS has its business address in Hagan.

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.