BIZTRAC BETA
Electrical installation

ÅMS EL SERVICE AS

Org. no. 912164772 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −21,000
Equity NOK −84,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−84k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

ÅMS EL SERVICE AS is registered as a limited company in Bærum, Akershus with organisation number 912164772. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Elektrisk installasjonsarbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK −84,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-563.3%
Weak
Equity as a share of total capital

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

Who owns ÅMS EL SERVICE AS?

ÅKE MARKUS VILHELM SVENSSON
ÅMS EL SERVICE AS
NOK 0 rev. · NOK −21,000 profit

ÅMS EL SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅMS EL SERVICE AS

Who owns ÅMS EL SERVICE AS?

ÅKE MARKUS VILHELM SVENSSON is the largest registered owner, with 100.0%.

What is the revenue of ÅMS EL SERVICE AS?

ÅMS EL SERVICE AS had revenue of NOK 0 in 2024.

Who is the general manager of ÅMS EL SERVICE AS?

Åke Markus Vilhelm Svensson is registered as general manager of ÅMS EL SERVICE AS.

Where is ÅMS EL SERVICE AS based?

ÅMS EL SERVICE AS has its business address in Kolsås.

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.