BIZTRAC BETA
Rental and operating of own or leased real estate

ALLOX AS

Org. no. 927831139 Limited company (AS) Sokndal Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 495,000
Operating profit NOK 215,000
Equity NOK 26,000
Incorporated 1981
Share capital NOK 100,000

ALLOX AS is registered as a limited company in Sokndal, Rogaland with organisation number 927831139. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon, service, handel, kjøp, salg, utleie og drift av fast eiendom, samt hva dermed måtte stå i forbindelse, herunder deltakelse i foretagender med tilnærmet samme formål, herunder også deltakelse gjennom aksjeerverv.”. The most recent filed accounts, for the 2025 financial year, show NOK 495,000 in revenue and NOK 215,000 in operating profit.

Key figures · 2025

Revenue
NOK 495,000
Operating profit
NOK 215,000
Equity
NOK 26,000
Est. value
NOK 242,000

Financial health · 2025

Liquidity
0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

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

Who owns ALLOX AS?

REKEFJORD MEK AS
ALLOX AS
NOK 495,000 rev. · NOK 215,000 profit

ALLOX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALLOX AS

Who owns ALLOX AS?

REKEFJORD MEK AS is the largest registered owner, with 100.0%.

What is the revenue of ALLOX AS?

ALLOX AS had revenue of NOK 495,000 in 2025.

Who is the general manager of ALLOX AS?

Frode André Mydland is registered as general manager of ALLOX AS.

Where is ALLOX AS based?

ALLOX AS has its business address in Hauge I Dalane.

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.