BIZTRAC BETA
COMPANY REGISTER PROFILE
835131122 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Repair and maintenance of motor vehicles

STENSVOLD AUTOSPA AS

Org. no. 835131122 Limited company (AS) Stord Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 683,000
Operating profit NOK 16,000
Equity NOK 38,000
Incorporated 2025
Share capital NOK 30,000

STENSVOLD AUTOSPA AS is registered as a limited company in Stord, Vestland with organisation number 835131122. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bilpleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 683,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 683,000
Operating profit
NOK 16,000
Equity
NOK 38,000
Est. value
NOK 84,000

Financial health · 2025

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.4%
Weak
Equity as a share of total capital

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

Who owns STENSVOLD AUTOSPA AS?

ANETTE AARRE STENSVOLD
STENSVOLD AUTOSPA AS
NOK 683,000 rev. · NOK 16,000 profit

STENSVOLD AUTOSPA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENSVOLD AUTOSPA AS

Who owns STENSVOLD AUTOSPA AS?

ANETTE AARRE STENSVOLD is the largest registered owner, with 100.0%.

What is the revenue of STENSVOLD AUTOSPA AS?

STENSVOLD AUTOSPA AS had revenue of NOK 683,000 in 2025.

Who is the general manager of STENSVOLD AUTOSPA AS?

Anette Aarre Stensvold is registered as general manager of STENSVOLD AUTOSPA AS.

Where is STENSVOLD AUTOSPA AS based?

STENSVOLD AUTOSPA AS has its business address in Sagvåg.

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.