BIZTRAC BETA
Uoppgitt

JPS INVEST AS

Org. no. 988978493 Limited company (AS) Tønsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −356,000
Equity NOK 17.0m
Incorporated 2005
Share capital NOK 130,000

Signals

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

JPS INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 988978493. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 130,000, divided into 130000 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investering i fast eiendom, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −356,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −356,000
Equity
NOK 17.0m
Est. value
NOK 12.3m

Financial health · 2025

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

Who owns JPS INVEST AS?

JAN PEDER KIRSEBOM STRANDMAN
JPS INVEST AS
NOK 0 rev. · NOK −356,000 profit

JPS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JPS INVEST AS own?

JPS INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about JPS INVEST AS

Who owns JPS INVEST AS?

JAN PEDER KIRSEBOM STRANDMAN is the largest registered owner, with 100.0%.

What is the revenue of JPS INVEST AS?

JPS INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of JPS INVEST AS?

Jan Peder Kirsebom Strandman is registered as general manager of JPS INVEST AS.

Where is JPS INVEST AS based?

JPS INVEST AS has its business address in Tønsberg.

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.