BIZTRAC BETA
Wholesale of other machinery and equipment

SEPLAMA AS

Org. no. 876911302 Limited company (AS) Larvik Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −278,000
Equity NOK −122,000
Incorporated 1996
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−122k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−278k kr).

SEPLAMA AS is registered as a limited company in Larvik, Vestfold with organisation number 876911302. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1996. Registered share capital is NOK 100,000. The company's stated purpose is: “Service, og operatøropplæring til plastindustrien, produksjonsoptimering/strukturering samt å være agent for utenlanske selskaper i Norge.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −278,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −278,000
Equity
NOK −122,000

Financial health · 2024

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

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

Who owns SEPLAMA AS?

PER WIDAR HVAAL
SEPLAMA AS
NOK 1.3m rev. · NOK −278,000 profit

SEPLAMA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEPLAMA AS

Who owns SEPLAMA AS?

PER WIDAR HVAAL is the largest registered owner, with 80.0%.

What is the revenue of SEPLAMA AS?

SEPLAMA AS had revenue of NOK 1.3m in 2024.

Who is the general manager of SEPLAMA AS?

Per Widar Hvaal is registered as general manager of SEPLAMA AS.

Where is SEPLAMA AS based?

SEPLAMA AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

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