BIZTRAC BETA
COMPANY REGISTER PROFILE
916454732 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ØSTHOLM AS

Org. no. 916454732 Limited company (AS) Austevoll Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 108,000
Operating profit NOK −1.4m
Equity NOK 46.3m
Incorporated 2015
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,4 mill kr).

ØSTHOLM AS is registered as a limited company in Austevoll, Vestland with organisation number 916454732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 1.8m, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 108,000 in revenue and NOK −1.4m in operating profit.

Former names: TOR HEINE ØSTERVOLD AS

Key figures · 2025

Revenue
NOK 108,000
▲ +0 %
Operating profit
NOK −1.4m
▼ −2 %
Equity
NOK 46.3m
▲ +2 %
Est. value
NOK 35.2m

Financial health · 2025

Liquidity
93.81
Very good
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
98.0%
Very good
Equity as a share of total capital

Who owns ØSTHOLM AS?

ØSTHOLM AS
NOK 108,000 rev. · NOK −1.4m profit

ØSTHOLM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØSTHOLM AS own?

ØSTHOLM AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about ØSTHOLM AS

Who owns ØSTHOLM AS?

TOR HEINE ØSTERVOLD is the largest registered owner, with 100.0%.

What is the revenue of ØSTHOLM AS?

ØSTHOLM AS had revenue of NOK 108,000 in 2025.

Where is ØSTHOLM AS based?

ØSTHOLM AS has its business address in Torangsvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.