BIZTRAC BETA
Construction of residential and non-residential buildings

ES BYGG OG EIENDOM AS

Org. no. 919498137 Limited company (AS) Østre Toten Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 239,000
Operating profit NOK 140,000
Equity NOK 265,000
Incorporated 2017
Share capital NOK 30,000

ES BYGG OG EIENDOM AS is registered as a limited company in Østre Toten, Innlandet with organisation number 919498137. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring av eiendom, graving og byggrelaterte tjenester og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 239,000 in revenue and NOK 140,000 in operating profit.

Key figures · 2025

Revenue
NOK 239,000
Operating profit
NOK 140,000
Equity
NOK 265,000
Est. value
NOK 322,000

Financial health · 2025

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

Who owns ES BYGG OG EIENDOM AS?

TOMMY ØSTBY SKJØLÅS
ES BYGG OG EIENDOM AS
NOK 239,000 rev. · NOK 140,000 profit

ES BYGG OG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ES BYGG OG EIENDOM AS

Who owns ES BYGG OG EIENDOM AS?

TOMMY ØSTBY SKJØLÅS is the largest registered owner, with 50.0%.

What is the revenue of ES BYGG OG EIENDOM AS?

ES BYGG OG EIENDOM AS had revenue of NOK 239,000 in 2025.

Who is the general manager of ES BYGG OG EIENDOM AS?

Tommy Østby Skjølås is registered as general manager of ES BYGG OG EIENDOM AS.

Where is ES BYGG OG EIENDOM AS based?

ES BYGG OG EIENDOM AS has its business address in Lena.

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.