BIZTRAC BETA
Rental and operating of own or leased real estate

ÅRVIKBRUKET EIENDOM AS

Org. no. 889340932 Limited company (AS) Skjervøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 258,000
Equity NOK 563,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅRVIKBRUKET EIENDOM AS is registered as a limited company in Skjervøy, Troms with organisation number 889340932. 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 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og utleie av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 258,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 258,000
Equity
NOK 563,000
Est. value
NOK 773,000

Financial health · 2024

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.3%
Satisfactory
Equity as a share of total capital

Who owns ÅRVIKBRUKET EIENDOM AS?

ALBRIGTSEN HOLDING AS
ÅRVIKBRUKET EIENDOM AS
NOK 1.2m rev. · NOK 258,000 profit

ÅRVIKBRUKET EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÅRVIKBRUKET EIENDOM AS

Who owns ÅRVIKBRUKET EIENDOM AS?

ALBRIGTSEN HOLDING AS is the largest registered owner, with 51.0%.

What is the revenue of ÅRVIKBRUKET EIENDOM AS?

ÅRVIKBRUKET EIENDOM AS had revenue of NOK 1.2m in 2024.

Where is ÅRVIKBRUKET EIENDOM AS based?

ÅRVIKBRUKET EIENDOM AS has its business address in Årviksand.

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.