biztrac. BETA
COMPANY REGISTER PROFILE
923171711 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Growing of other perennial crops

PROTON MASKIN OG UTEMILJØ AS

Org. no. 923171711 Limited company (AS) Bærum Incorporated 2019 Active
Operating profit NOK −23,000
Equity NOK −27,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

PROTON MASKIN OG UTEMILJØ AS is registered as a limited company in Bærum, Akershus with organisation number 923171711. The business is classified under growing of other perennial crops (NACE 01.290). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon og salg av sedum og andre gressprodukter, samt maskinentreprenør-tjenester og anleggsgartnervirksomhet.”.

Former names: SEDUMSENTERET AS, HAJAC MASKIN AS, PROTON MASKIN AS

Key figures · 2025

Operating profit
NOK −23,000
Equity
NOK −27,000
▼ −650 %

Financial health · 2025

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

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

Who owns PROTON MASKIN OG UTEMILJØ AS?

PROTON MASKIN OG UTEMILJØ AS
· NOK −23,000 profit

PROTON MASKIN OG UTEMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROTON MASKIN OG UTEMILJØ AS

Who owns PROTON MASKIN OG UTEMILJØ AS?

KARBON HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of PROTON MASKIN OG UTEMILJØ AS?

Finn Thomas Jacobsen is registered as general manager of PROTON MASKIN OG UTEMILJØ AS.

Where is PROTON MASKIN OG UTEMILJØ AS based?

PROTON MASKIN OG UTEMILJØ AS has its business address in Lommedalen.

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.