BIZTRAC BETA
Computer programming activities

AM DEVELOPMENT AS

Org. no. 929434285 Limited company (AS) Horten Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 67,000
Operating profit NOK −7,000
Equity NOK 16,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

AM DEVELOPMENT AS is registered as a limited company in Horten, Vestfold with organisation number 929434285. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og drifting av webtjenester, salg av utstyr knyttet mot dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 67,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 67,000
Operating profit
NOK −7,000
Equity
NOK 16,000
Est. value
NOK 121,000

Financial health · 2025

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

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

Who owns AM DEVELOPMENT AS?

ALEKSANDER MOHOLT
AM DEVELOPMENT AS
NOK 67,000 rev. · NOK −7,000 profit

AM DEVELOPMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AM DEVELOPMENT AS

Who owns AM DEVELOPMENT AS?

ALEKSANDER MOHOLT is the largest registered owner, with 100.0%.

What is the revenue of AM DEVELOPMENT AS?

AM DEVELOPMENT AS had revenue of NOK 67,000 in 2025.

Who is the general manager of AM DEVELOPMENT AS?

Aleksander Moholt is registered as general manager of AM DEVELOPMENT AS.

Where is AM DEVELOPMENT AS based?

AM DEVELOPMENT AS has its business address in Skoppum.

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.