BIZTRAC BETA
Rental and operating of own or leased real estate

E VERMELID AS

Org. no. 942185960 Limited company (AS) Trondheim Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.1m
Equity NOK 2.9m
Incorporated 1987
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

E VERMELID AS is registered as a limited company in Trondheim, Trøndelag with organisation number 942185960. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Å drive virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.1m
Equity
NOK 2.9m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns E VERMELID AS?

SERE III NORWEGIAN RETAIL AS
E VERMELID AS
NOK 2.2m rev. · NOK 1.1m profit

E VERMELID AS has 1 registered shareholder:

All shareholders and roles →

Group structure

E VERMELID AS er morselskap for 249 datterselskaper:

Frequently asked questions about E VERMELID AS

Who owns E VERMELID AS?

SERE III NORWEGIAN RETAIL AS is the largest registered owner, with 100.0%.

What is the revenue of E VERMELID AS?

E VERMELID AS had revenue of NOK 2.2m in 2024.

Where is E VERMELID AS based?

E VERMELID AS has its business address in Trondheim.

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.