BIZTRAC BETA
Combined facilities support activities

OKSEDALSSTEIN AS

Org. no. 986206876 Limited company (AS) Lillesand Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 619,000
Operating profit NOK 28,000
Equity NOK 1.0m
Incorporated 2003
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-27 Aksjekapital registrert 2026-05-27.

OKSEDALSSTEIN AS is registered as a limited company in Lillesand, Agder with organisation number 986206876. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2003. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Vaktmestertjenester herunder snekring, muring og annet vedlikehold av fast eiendom. Samt andre tjenester som faller naturlig i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 619,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 619,000
Operating profit
NOK 28,000
Equity
NOK 1.0m
Est. value
NOK 674,000

Financial health · 2025

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

Who owns OKSEDALSSTEIN AS?

OLE MAGNUS BEKKEVIK
OKSEDALSSTEIN AS
NOK 619,000 rev. · NOK 28,000 profit

OKSEDALSSTEIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OKSEDALSSTEIN AS

Who owns OKSEDALSSTEIN AS?

OLE MAGNUS BEKKEVIK is the largest registered owner, with 100.0%.

What is the revenue of OKSEDALSSTEIN AS?

OKSEDALSSTEIN AS had revenue of NOK 619,000 in 2025.

Who is the general manager of OKSEDALSSTEIN AS?

Ole Magnus Bekkevik is registered as general manager of OKSEDALSSTEIN AS.

Where is OKSEDALSSTEIN AS based?

OKSEDALSSTEIN AS has its business address in Brekkestø.

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.