biztrac. BETA
COMPANY REGISTER PROFILE
933413322 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other intermediate products

SLUPPAN AS

Org. no. 933413322 Limited company (AS) Kragerø Incorporated 1983 Active
Revenue 2025 NOK 2.2m
Operating profit NOK 1.3m
Equity NOK 1.8m
Incorporated 1983
Share capital NOK 1.1m

Signals

1 flags
  • Nylig endring 2026-08-20 Adresseendring registrert 2026-08-20.

SLUPPAN AS is registered as a limited company in Kragerø, Telemark with organisation number 933413322. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 1983. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Handel, produksjon og hva som står i forbindelse med dette, samt å delta i andre selskaper/juridiske personer. Dessuten skal selskapet eie fast eiendom, drive eiendomsutvikling, utleie av fast eiendom og annen virksomhet som står i naturlig tilknytning til dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.3m in operating profit.

Former names: FINN CARLSEN AS

Key figures · 2025

Revenue
NOK 2.2m
▲ +2 %
Operating profit
NOK 1.3m
▲ +2 %
Equity
NOK 1.8m
▼ −41 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
2.32
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

Who owns SLUPPAN AS?

SLUPPAN AS
NOK 2.2m rev. · NOK 1.3m profit

SLUPPAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLUPPAN AS

Who owns SLUPPAN AS?

BIED AS is the largest registered owner, with 100.0%.

What is the revenue of SLUPPAN AS?

SLUPPAN AS had revenue of NOK 2.2m in 2025.

Where is SLUPPAN AS based?

SLUPPAN AS has its business address in Kragerø.

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.