BIZTRAC BETA
Civil engineering activities

AKSE AS

Org. no. 992820284 Limited company (AS) Kristiansand Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 78,000
Operating profit NOK 2,000
Equity NOK −100,000
Incorporated 2008
Share capital NOK 110,000

Signals

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

AKSE AS is registered as a limited company in Kristiansand, Agder with organisation number 992820284. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2008. Registered share capital is NOK 110,000, divided into 110 shares. The company's stated purpose is: “Omsetning av varer og tjenester knyttet til byggevirksomhet, herunder eierskap til eierandeler i selskaper som har tilsvarende hovedvirksomhet, samt virksomhet som naturlig kan knyttes til slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 78,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 78,000
Operating profit
NOK 2,000
Equity
NOK −100,000
Est. value
NOK 7,000

Financial health · 2025

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

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

Who owns AKSE AS?

ARNSTEIN RØSSTAD
AKSE AS
NOK 78,000 rev. · NOK 2,000 profit

AKSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKSE AS

Who owns AKSE AS?

ARNSTEIN RØSSTAD is the largest registered owner, with 100.0%.

What is the revenue of AKSE AS?

AKSE AS had revenue of NOK 78,000 in 2025.

Who is the general manager of AKSE AS?

Arnstein Røsstad is registered as general manager of AKSE AS.

Where is AKSE AS based?

AKSE AS has its business address in Kristiansand S.

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.