biztrac. BETA
COMPANY REGISTER PROFILE
880154532 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of plastic plates, sheets, tubes and profiles

SKUMPLAST SENTERET AS

Org. no. 880154532 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 454,000
Equity NOK 198,000
Incorporated 1998
Share capital NOK 30,000

SKUMPLAST SENTERET AS is registered as a limited company in Oslo, Oslo with organisation number 880154532. The business is classified under manufacture of plastic plates, sheets, tubes and profiles (NACE 22.210). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Handel, agentur, produksjons- og konsulentvirksomhet, samt det som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 454,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
▲ +21 %
Operating profit
NOK 454,000
▲ +134 %
Equity
NOK 198,000
▼ −55 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
40.0%
Very good
Return on total assets
Solidity
14.2%
Satisfactory
Equity as a share of total capital

Who owns SKUMPLAST SENTERET AS?

SKUMPLAST SENTERET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKUMPLAST SENTERET AS

Who owns SKUMPLAST SENTERET AS?

Kjetil Andreas Mikalsen is the largest registered owner, with 34.0%.

What is the revenue of SKUMPLAST SENTERET AS?

SKUMPLAST SENTERET AS had revenue of NOK 3.2m in 2025.

Who is the general manager of SKUMPLAST SENTERET AS?

Arnfred Mikal Mikalsen is registered as general manager of SKUMPLAST SENTERET AS.

Where is SKUMPLAST SENTERET AS based?

SKUMPLAST SENTERET 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.