BIZTRAC BETA
COMPANY REGISTER PROFILE
983829589 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Manufacture of other general-purpose machinery n.e.c.

J MANNERÅK SMIE & SVEISESERVICE AS

Org. no. 983829589 Limited company (AS) Lindesnes Incorporated 2001 Active
Ownership graph ↗
Equity NOK −516,000
Incorporated 2001
Share capital NOK 100,000

Signals

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

J MANNERÅK SMIE & SVEISESERVICE AS is registered as a limited company in Lindesnes, Agder with organisation number 983829589. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon, salg og import av smijernsprodukter, verkstedvirksomhet og hva hermed står i naturlig forbindelse.”.

Key figures · 2025

Equity
NOK −516,000
▲ +0 %

Financial health · 2025

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

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

Who owns J MANNERÅK SMIE & SVEISESERVICE AS?

J MANNERÅK SMIE & SVEISESERVICE AS

J MANNERÅK SMIE & SVEISESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J MANNERÅK SMIE & SVEISESERVICE AS

Who owns J MANNERÅK SMIE & SVEISESERVICE AS?

Jarl Jakobsen Manneråk is the largest registered owner, with 100.0%.

Who is the general manager of J MANNERÅK SMIE & SVEISESERVICE AS?

Jarl Jakobsen Manneråk is registered as general manager of J MANNERÅK SMIE & SVEISESERVICE AS.

Where is J MANNERÅK SMIE & SVEISESERVICE AS based?

J MANNERÅK SMIE & SVEISESERVICE AS has its business address in Marnardal.

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

Report a problem

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