BIZTRAC BETA
Rental and operating of own or leased real estate

OKSDØL EIENDOM AS

Org. no. 928600467 Limited company (AS) Namsos Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 146,000
Operating profit NOK 11,000
Equity NOK 108,000
Incorporated 2021
Share capital NOK 30,000

OKSDØL EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 928600467. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i, herunder erverv, utvikling, utleie og forvaltning av fast eiendom. Selskapet kan med aksjeinnskudd eller på annen måte delta i virksomhet med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 146,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 146,000
Operating profit
NOK 11,000
Equity
NOK 108,000
Est. value
NOK 102,000

Financial health · 2025

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

Who owns OKSDØL EIENDOM AS?

MARTIN KRISTIAN OKSDØL
OKSDØL EIENDOM AS
NOK 146,000 rev. · NOK 11,000 profit

OKSDØL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OKSDØL EIENDOM AS

Who owns OKSDØL EIENDOM AS?

MARTIN KRISTIAN OKSDØL is the largest registered owner, with 50.0%.

What is the revenue of OKSDØL EIENDOM AS?

OKSDØL EIENDOM AS had revenue of NOK 146,000 in 2025.

Who is the general manager of OKSDØL EIENDOM AS?

Martin Kristian Oksdøl is registered as general manager of OKSDØL EIENDOM AS.

Where is OKSDØL EIENDOM AS based?

OKSDØL EIENDOM AS has its business address in Nord-Statland.

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.