BIZTRAC BETA
Development of building projects

AK RÅDGIVNING AS

Org. no. 915753078 Limited company (AS) Nes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −5,000
Equity NOK 91,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

AK RÅDGIVNING AS is registered as a limited company in Nes, Akershus with organisation number 915753078. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i andre selskaper samt forvaltning av økonomiske verdier og midler. I dette ligger rådgivning til selskaper og personlige næringsdrivende. Man vil også ta del i andre selskaper der dette gir et faglig og økonomisk utbytte.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −5,000
Equity
NOK 91,000
Est. value
NOK 64,000

Financial health · 2025

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

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

Who owns AK RÅDGIVNING AS?

TØRN INVEST AS
AK RÅDGIVNING AS
NOK 2,000 rev. · NOK −5,000 profit

AK RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AK RÅDGIVNING AS

Who owns AK RÅDGIVNING AS?

TØRN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of AK RÅDGIVNING AS?

AK RÅDGIVNING AS had revenue of NOK 2,000 in 2025.

Where is AK RÅDGIVNING AS based?

AK RÅDGIVNING AS has its business address in Årnes.

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.