biztrac. BETA
COMPANY REGISTER PROFILE
998283590 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

J. S. LARSEN AS

Org. no. 998283590 Limited company (AS) Fredrikstad Incorporated 2012 Active
Revenue 2025 NOK 299,000
Operating profit NOK −45,000
Equity NOK 92,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

J. S. LARSEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 998283590. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Maskinentreprenør.”. The most recent filed accounts, for the 2025 financial year, show NOK 299,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 299,000
▼ −13 %
Operating profit
NOK −45,000
▲ +37 %
Equity
NOK 92,000
▼ −33 %
Est. value
NOK 144,000

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
-12.2%
Not satisfactory
Return on total assets
Solidity
27.5%
Weak
Equity as a share of total capital

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

Who owns J. S. LARSEN AS?

J. S. LARSEN AS
NOK 299,000 rev. · NOK −45,000 profit

J. S. LARSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about J. S. LARSEN AS

Who owns J. S. LARSEN AS?

Jan Sverre Larsen is the largest registered owner, with 60.0%.

What is the revenue of J. S. LARSEN AS?

J. S. LARSEN AS had revenue of NOK 299,000 in 2025.

Who is the general manager of J. S. LARSEN AS?

Jan Sverre Larsen is registered as general manager of J. S. LARSEN AS.

Where is J. S. LARSEN AS based?

J. S. LARSEN AS has its business address in Manstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.