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

PLENKLIPPEREN.NO AS

Org. no. 915116817 Limited company (AS) Bergen Incorporated 2015 Active
Revenue 2025 NOK 2.7m
Operating profit NOK −137,000
Equity NOK −557,000
Incorporated 2015
Employees 7
Share capital NOK 30,000

Signals

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

PLENKLIPPEREN.NO AS is registered as a limited company in Bergen, Vestland with organisation number 915116817. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2015 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vedlikehold av grøntområder og alt som står naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −137,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +15 %
Operating profit
NOK −137,000
▼ −52 %
Equity
NOK −557,000
▼ −24 %

Financial health · 2025

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

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

Who owns PLENKLIPPEREN.NO AS?

PLENKLIPPEREN.NO AS
NOK 2.7m rev. · NOK −137,000 profit

PLENKLIPPEREN.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PLENKLIPPEREN.NO AS

Who owns PLENKLIPPEREN.NO AS?

Gard Storeide is the largest registered owner, with 100.0%.

What is the revenue of PLENKLIPPEREN.NO AS?

PLENKLIPPEREN.NO AS had revenue of NOK 2.7m in 2025.

Where is PLENKLIPPEREN.NO AS based?

PLENKLIPPEREN.NO AS has its business address in Sandsli.

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.