BIZTRAC BETA
Business and other management consultancy activities

AKIBA AS

Org. no. 995958732 Limited company (AS) Sandnes Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −41,000
Equity NOK 2.5m
Incorporated 2010
Share capital NOK 250,000

Signals

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

AKIBA AS is registered as a limited company in Sandnes, Rogaland with organisation number 995958732. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010. Registered share capital is NOK 250,000, divided into 200000 shares. The company's stated purpose is: “Konsultenttjenester innen administrative og økonomiske fagfelt samt investeringsvirksomhet, herunder å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −41,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −41,000
Equity
NOK 2.5m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns AKIBA AS?

ARILD OLLESTAD
AKIBA AS
NOK 0 rev. · NOK −41,000 profit

AKIBA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AKIBA AS own?

AKIBA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AKIBA AS

Who owns AKIBA AS?

ARILD OLLESTAD is the largest registered owner, with 100.0%.

What is the revenue of AKIBA AS?

AKIBA AS had revenue of NOK 0 in 2025.

Who is the general manager of AKIBA AS?

Arild Ollestad is registered as general manager of AKIBA AS.

Where is AKIBA AS based?

AKIBA AS has its business address in Sandnes.

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.