BIZTRAC BETA
COMPANY REGISTER PROFILE
918082360 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

PANTER INVEST AS

Org. no. 918082360 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 114,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

PANTER INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 918082360. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Deltagelse i andre virksomheter samt hva som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 114,000
Est. value
NOK 228,000

Financial health · 2024

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

Who owns PANTER INVEST AS?

MORTEN GRUSD
PANTER INVEST AS
NOK 0 rev. · NOK −10,000 profit

PANTER INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PANTER INVEST AS own?

PANTER INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PANTER INVEST AS

Who owns PANTER INVEST AS?

MORTEN GRUSD is the largest registered owner, with 100.0%.

What is the revenue of PANTER INVEST AS?

PANTER INVEST AS had revenue of NOK 0 in 2024.

Where is PANTER INVEST AS based?

PANTER INVEST AS has its business address in Bekkestua.

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.