BIZTRAC BETA
Uoppgitt

ARETO CONSULTING AS

Org. no. 991315969 Limited company (AS) Øygarden Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 45,000
Operating profit NOK 44,000
Equity NOK 179,000
Incorporated 2007
Share capital NOK 30,000

ARETO CONSULTING AS is registered as a limited company in Øygarden, Vestland with organisation number 991315969. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2007. Registered share capital is NOK 30,000, divided into 11945 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer, investere i eiendom og ha deltakerinteressert i andre selskaper, samt alt hva står i forbindelse med dette. Selskapet skal også kunne levere bedriftsøkonomiske konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 45,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 45,000
Operating profit
NOK 44,000
Equity
NOK 179,000
Est. value
NOK 202,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.3%
Satisfactory
Equity as a share of total capital

Who owns ARETO CONSULTING AS?

FRODE SEKKINGSTAD
ARETO CONSULTING AS
NOK 45,000 rev. · NOK 44,000 profit

ARETO CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARETO CONSULTING AS

Who owns ARETO CONSULTING AS?

FRODE SEKKINGSTAD is the largest registered owner, with 50.0%.

What is the revenue of ARETO CONSULTING AS?

ARETO CONSULTING AS had revenue of NOK 45,000 in 2025.

Who is the general manager of ARETO CONSULTING AS?

Frode Sekkingstad is registered as general manager of ARETO CONSULTING AS.

Where is ARETO CONSULTING AS based?

ARETO CONSULTING AS has its business address in Tjeldstø.

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.