BIZTRAC BETA
Security activities n.e.c.

ATLANTIX AS

Org. no. 925832316 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −28,000
Equity NOK 34,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ATLANTIX AS is registered as a limited company in Bergen, Vestland with organisation number 925832316. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive konsulent og kursvirksomhet innen HMS, ledelse og maritime fag og annet som naturlig faller sammen med dette, herunder kjøp og salg av verdipapirer eller andre foretak, samt investering i eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −28,000
Equity
NOK 34,000
Est. value
NOK 22,000

Financial health · 2024

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.2%
Weak
Equity as a share of total capital

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

Who owns ATLANTIX AS?

GØRAN FURLAND
ATLANTIX AS
NOK 7,000 rev. · NOK −28,000 profit

ATLANTIX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATLANTIX AS

Who owns ATLANTIX AS?

GØRAN FURLAND is the largest registered owner, with 100.0%.

What is the revenue of ATLANTIX AS?

ATLANTIX AS had revenue of NOK 7,000 in 2024.

Who is the general manager of ATLANTIX AS?

Gøran Furland is registered as general manager of ATLANTIX AS.

Where is ATLANTIX AS based?

ATLANTIX AS has its business address in Bønes.

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.