biztrac. BETA
COMPANY REGISTER PROFILE
990593744 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

PETTCON AS

Org. no. 990593744 Limited company (AS) Alstahaug Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −233,000
Incorporated 2006
Share capital NOK 110,000

Signals

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

PETTCON AS is registered as a limited company in Alstahaug, Nordland with organisation number 990593744. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 110,000, divided into 110 shares. The company's stated purpose is: “Å drive konsulentvirksomhet og utleie av fast eiendom, herunder eie aksjer og eiendommer samt relaterte tjenester.”.

Key figures · 2024

Operating profit
NOK −4,000
▲ +96 %
Equity
NOK −233,000
▼ −2 %

Financial health · 2024

Liquidity
29.53
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-19.2%
Weak
Equity as a share of total capital

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

Who owns PETTCON AS?

PETTCON AS
· NOK −4,000 profit

PETTCON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PETTCON AS own?

PETTCON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PETTCON AS

Who owns PETTCON AS?

Oddvar Johan Pettersen is the largest registered owner, with 100.0%.

Who is the general manager of PETTCON AS?

Oddvar Johan Pettersen is registered as general manager of PETTCON AS.

Where is PETTCON AS based?

PETTCON AS has its business address in Sandnessjøen.

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.