biztrac. BETA
COMPANY REGISTER PROFILE
821117372 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠ÅSVIKA UTVIKLING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Development of building projects

ÅSVIKA UTVIKLING AS

Org. no. 821117372 Limited company (AS) Porsgrunn Incorporated 2018 In liquidation
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 134,000
Incorporated 2018
Share capital NOK 100,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅSVIKA UTVIKLING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 821117372. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling og byggevirksomhet, kjøp, salg og drift av fast eiendom, samt annen virksomhet som står i naturlig sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −61,000
▲ +51 %
Equity
NOK 134,000
▼ −8 %

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

Who owns ÅSVIKA UTVIKLING AS?

ÅSVIKA UTVIKLING AS
· NOK −61,000 profit

ÅSVIKA UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅSVIKA UTVIKLING AS

Who owns ÅSVIKA UTVIKLING AS?

FJELLSTØ GRUPPEN AS is the largest registered owner, with 100.0%.

Where is ÅSVIKA UTVIKLING AS based?

ÅSVIKA UTVIKLING AS has its business address in Porsgrunn.

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.