biztrac. BETA
COMPANY REGISTER PROFILE
991168788 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

PARKMASKINER AS

Org. no. 991168788 Limited company (AS) Færder Incorporated 2007 Active
Revenue 2025 NOK 5.5m
Operating profit NOK −379,000
Equity NOK 340,000
Incorporated 2007
Employees 5
Share capital NOK 200,000

Signals

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

PARKMASKINER AS is registered as a limited company in Færder, Vestfold with organisation number 991168788. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2007 and has 5 registered employees. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Salg av maskiner til idretts- og parkanlegg og det som naturlig hører innunder dette, samt konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK −379,000 in operating profit.

Former names: TMG SPORTSDEKKE AS

Key figures · 2025

Revenue
NOK 5.5m
▲ +19 %
Operating profit
NOK −379,000
▼ −280 %
Equity
NOK 340,000
▼ −58 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
-14.1%
Not satisfactory
Return on total assets
Solidity
11.7%
Satisfactory
Equity as a share of total capital

Who owns PARKMASKINER AS?

PARKMASKINER AS
NOK 5.5m rev. · NOK −379,000 profit

PARKMASKINER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PARKMASKINER AS

Who owns PARKMASKINER AS?

Tor Mjøen is the largest registered owner, with 70.0%.

What is the revenue of PARKMASKINER AS?

PARKMASKINER AS had revenue of NOK 5.5m in 2025.

Where is PARKMASKINER AS based?

PARKMASKINER AS has its business address in Vestskogen.

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.