BIZTRAC BETA
Work training and permanently adapted work

FOLKI ARBEID AS

Org. no. 930088951 Limited company (AS) Tjeldsund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK −84,000
Equity NOK 3.2m
Incorporated 2022
Employees 24
Share capital NOK 100,000

Signals

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

FOLKI ARBEID AS is registered as a limited company in Tjeldsund, Troms with organisation number 930088951. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 2022 and has 24 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Allmennyttig kompetanseselskap som har arbeidsinkludering, arbeidstrening, utvikling og videreutvikling av arbeidskompetanse som hovedmålsetning. Selskapet har ikke erverv som formål og er underlagt utbytteforbud.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK −84,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK −84,000
Equity
NOK 3.2m
Est. value
NOK 8.5m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.8%
Very good
Equity as a share of total capital

Who owns FOLKI ARBEID AS?

No shareholders are registered for FOLKI ARBEID AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FOLKI ARBEID AS

What is the revenue of FOLKI ARBEID AS?

FOLKI ARBEID AS had revenue of NOK 16.1m in 2024.

Who is the general manager of FOLKI ARBEID AS?

Astrid Berg is registered as general manager of FOLKI ARBEID AS.

Where is FOLKI ARBEID AS based?

FOLKI ARBEID AS has its business address in Evenskjer.

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.