BIZTRAC BETA
Other information technology and computer service activities

AME FORTIFY AS

Org. no. 933296075 Limited company (AS) Kvinnherad Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

AME FORTIFY AS is registered as a limited company in Kvinnherad, Vestland with organisation number 933296075. The business is classified under other information technology and computer service activities (NACE 62.900). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −11,000
Equity
NOK 19,000
Est. value
NOK 35,000

Financial health · 2024

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

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

Who owns AME FORTIFY AS?

ESPEN BAUGE
AME FORTIFY AS
· NOK −11,000 profit

AME FORTIFY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AME FORTIFY AS own?

AME FORTIFY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AME FORTIFY AS

Who owns AME FORTIFY AS?

ESPEN BAUGE is the largest registered owner, with 100.0%.

Who is the general manager of AME FORTIFY AS?

Espen Bauge is registered as general manager of AME FORTIFY AS.

Where is AME FORTIFY AS based?

AME FORTIFY AS has its business address in Valen.

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.