BIZTRAC BETA
Sports and recreation education

BIG P INVEST AS

Org. no. 921312717 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 40,000
Operating profit NOK 33,000
Equity NOK −95,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−95k kr).

BIG P INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 921312717. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Direkte eller gjennom datterselskaper å investere i fast eiendom, aksjer, andre verdipapirer og all virksomhet som står i forbindelse med dette, samt drive konsulentvirksomhet innenfor innebandy, trening og kosthold.”. The most recent filed accounts, for the 2025 financial year, show NOK 40,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 40,000
Operating profit
NOK 33,000
Equity
NOK −95,000
Est. value
NOK 135,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-13.6%
Weak
Equity as a share of total capital

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

Who owns BIG P INVEST AS?

LARS PATRIC JONSSON
BIG P INVEST AS
NOK 40,000 rev. · NOK 33,000 profit

BIG P INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIG P INVEST AS

Who owns BIG P INVEST AS?

LARS PATRIC JONSSON is the largest registered owner, with 100.0%.

What is the revenue of BIG P INVEST AS?

BIG P INVEST AS had revenue of NOK 40,000 in 2025.

Where is BIG P INVEST AS based?

BIG P INVEST AS has its business address in Oslo.

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.