BIZTRAC BETA
Security and commodity contracts brokerage

AA & SP RÅDGIVNING AS

Org. no. 925478768 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 21.1m
Operating profit NOK 6.5m
Equity NOK 4.7m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AA & SP RÅDGIVNING AS is registered as a limited company in Oslo, Oslo with organisation number 925478768. The business is classified under security and commodity contracts brokerage (NACE 66.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby investeringsrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.1m in revenue and NOK 6.5m in operating profit.

Key figures · 2025

Revenue
NOK 21.1m
Operating profit
NOK 6.5m
Equity
NOK 4.7m
Est. value
NOK 20.3m

Financial health · 2025

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

Who owns AA & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS
AA & SP RÅDGIVNING AS
NOK 21.1m rev. · NOK 6.5m profit

AA & SP RÅDGIVNING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AA & SP RÅDGIVNING AS

Who owns AA & SP RÅDGIVNING AS?

FH KAPITAL HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of AA & SP RÅDGIVNING AS?

AA & SP RÅDGIVNING AS had revenue of NOK 21.1m in 2025.

Who is the general manager of AA & SP RÅDGIVNING AS?

Asbjørn Aas is registered as general manager of AA & SP RÅDGIVNING AS.

Where is AA & SP RÅDGIVNING AS based?

AA & SP RÅDGIVNING AS has its business address in Oslo.

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.