biztrac. BETA
COMPANY REGISTER PROFILE
933380068 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

AME SUPPLY AS

Org. no. 933380068 Limited company (AS) Horten Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK −951,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−951k kr).

AME SUPPLY AS is registered as a limited company in Horten, Vestfold with organisation number 933380068. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette. Konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
▼ −180 %
Equity
NOK −951,000
▼ −0 %

Financial health · 2025

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

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

Who owns AME SUPPLY AS?

AME SUPPLY AS
NOK 0 rev. · NOK −3,000 profit

AME SUPPLY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AME SUPPLY AS own?

AME SUPPLY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AME SUPPLY AS

Who owns AME SUPPLY AS?

Anna Maria Elisabeth Söderpalm is the largest registered owner, with 100.0%.

What is the revenue of AME SUPPLY AS?

AME SUPPLY AS had revenue of NOK 0 in 2025.

Where is AME SUPPLY AS based?

AME SUPPLY AS has its business address in Horten.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.