BIZTRAC BETA
Rental and operating of own or leased real estate

ØVERMARK INVEST AS

Org. no. 832356522 Limited company (AS) Sortland Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 164,000
Operating profit NOK 59,000
Equity NOK 71,000
Incorporated 2023
Share capital NOK 30,000

ØVERMARK INVEST AS is registered as a limited company in Sortland, Nordland with organisation number 832356522. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 164,000 in revenue and NOK 59,000 in operating profit.

Key figures · 2024

Revenue
NOK 164,000
Operating profit
NOK 59,000
Equity
NOK 71,000
Est. value
NOK 197,000

Financial health · 2024

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

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

Who owns ØVERMARK INVEST AS?

ØVERGÅRD INVEST AS
ØVERMARK INVEST AS
NOK 164,000 rev. · NOK 59,000 profit

ØVERMARK INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØVERMARK INVEST AS

Who owns ØVERMARK INVEST AS?

ØVERGÅRD INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of ØVERMARK INVEST AS?

ØVERMARK INVEST AS had revenue of NOK 164,000 in 2024.

Where is ØVERMARK INVEST AS based?

ØVERMARK INVEST AS has its business address in Sortland.

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.