BIZTRAC BETA
Buying and selling of own real estate

AME UTVIKLING AS

Org. no. 936094392 Limited company (AS) Evenes Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 102,000
Operating profit NOK 36,000
Equity NOK 53,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-08-22.

AME UTVIKLING AS is registered as a limited company in Evenes, Nordland with organisation number 936094392. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, investering og drift av virksomheter innen eiendom, handel, tjenester og industri, samt annen virksomhet som naturlig hører sammen med dette. Selskapet kan eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 102,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 102,000
Operating profit
NOK 36,000
Equity
NOK 53,000
Est. value
NOK 130,000

Financial health · 2025

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

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

Who owns AME UTVIKLING AS?

A.M.ERIKSEN HOLDING AS
AME UTVIKLING AS
NOK 102,000 rev. · NOK 36,000 profit

AME UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AME UTVIKLING AS

Who owns AME UTVIKLING AS?

A.M.ERIKSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AME UTVIKLING AS?

AME UTVIKLING AS had revenue of NOK 102,000 in 2025.

Where is AME UTVIKLING AS based?

AME UTVIKLING AS has its business address in Liland.

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.