BIZTRAC BETA
Joinery installation

JO STORSTEN SERVICE AS

Org. no. 998079179 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 657,000
Operating profit NOK 10,000
Equity NOK 39,000
Incorporated 2012
Share capital NOK 30,000

JO STORSTEN SERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998079179. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av snekkertjenester, levering av varer i tilknytning til dette samt hva hermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 657,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 657,000
Operating profit
NOK 10,000
Equity
NOK 39,000
Est. value
NOK 52,000

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.2%
Weak
Equity as a share of total capital

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

Who owns JO STORSTEN SERVICE AS?

JO STORSTEN
JO STORSTEN SERVICE AS
NOK 657,000 rev. · NOK 10,000 profit

JO STORSTEN SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JO STORSTEN SERVICE AS

Who owns JO STORSTEN SERVICE AS?

JO STORSTEN is the largest registered owner, with 100.0%.

What is the revenue of JO STORSTEN SERVICE AS?

JO STORSTEN SERVICE AS had revenue of NOK 657,000 in 2025.

Who is the general manager of JO STORSTEN SERVICE AS?

Jo Storsten is registered as general manager of JO STORSTEN SERVICE AS.

Where is JO STORSTEN SERVICE AS based?

JO STORSTEN SERVICE AS has its business address in Heimdal.

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.