BIZTRAC BETA
Rental and operating of own or leased real estate

ARBEIDER'N AS

Org. no. 893230122 Limited company (AS) Vågan Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −164,000
Equity NOK 1.1m
Incorporated 2008
Share capital NOK 890,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−164k kr).

ARBEIDER'N AS is registered as a limited company in Vågan, Nordland with organisation number 893230122. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 890,000, divided into 890 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, restaurant- og kafedrift, arrangere konserter, utleie av lokalet, og alt som naturlig faller inn under slik type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −164,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −164,000
Equity
NOK 1.1m
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
69.3%
Very good
Equity as a share of total capital

Who owns ARBEIDER'N AS?

ARNE ANDREASEN
ARBEIDER'N AS
NOK 1.4m rev. · NOK −164,000 profit

ARBEIDER'N AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARBEIDER'N AS

Who owns ARBEIDER'N AS?

ARNE ANDREASEN is the largest registered owner, with 66.3%.

What is the revenue of ARBEIDER'N AS?

ARBEIDER'N AS had revenue of NOK 1.4m in 2024.

Who is the general manager of ARBEIDER'N AS?

Arne Andreasen is registered as general manager of ARBEIDER'N AS.

Where is ARBEIDER'N AS based?

ARBEIDER'N AS has its business address in Kabelvåg.

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.