BIZTRAC BETA
Civil engineering activities

ESMAS AS

Org. no. 933163466 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 112,000
Equity NOK 211,000
Incorporated 2024
Share capital NOK 30,000

ESMAS AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933163466. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Generell konsulenttjenester og teknisk rådgivning innen bygg og anlegg, samt med eiendom drift-, forvaltning-, vedlikehold- og utviklingstjenester, prosjektledelse og alt hva hermed står i forbindelse med dette. Hovedentreprise av bygninger og installasjoner på vei av privat og næringskunder. Selskapet kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 112,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 112,000
Equity
NOK 211,000
Est. value
NOK 661,000

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.7%
Good
Equity as a share of total capital

Who owns ESMAS AS?

EDVINAS MASIOTAS
ESMAS AS
NOK 1.0m rev. · NOK 112,000 profit

ESMAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESMAS AS

Who owns ESMAS AS?

EDVINAS MASIOTAS is the largest registered owner, with 100.0%.

What is the revenue of ESMAS AS?

ESMAS AS had revenue of NOK 1.0m in 2025.

Who is the general manager of ESMAS AS?

Edvinas Masiotas is registered as general manager of ESMAS AS.

Where is ESMAS AS based?

ESMAS AS has its business address in Skodje.

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.