biztrac. BETA
COMPANY REGISTER PROFILE
989268899 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

BORNTORUNE AS

Org. no. 989268899 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −91,000
Equity NOK 33.0m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−91k kr).

BORNTORUNE AS is registered as a limited company in Bergen, Vestland with organisation number 989268899. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom og andre eiendeler som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −91,000 in operating profit.

Former names: SKARSTEIN INVEST AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −91,000
▼ −83 %
Equity
NOK 33.0m
▲ +0 %
Est. value
NOK 19.9m

Financial health · 2025

Liquidity
4.28
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
98.1%
Very good
Equity as a share of total capital

Who owns BORNTORUNE AS?

BORNTORUNE AS
NOK 0 rev. · NOK −91,000 profit

BORNTORUNE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BORNTORUNE AS own?

BORNTORUNE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BORNTORUNE AS

Who owns BORNTORUNE AS?

Rune Skarstein is the largest registered owner, with 100.0%.

What is the revenue of BORNTORUNE AS?

BORNTORUNE AS had revenue of NOK 0 in 2025.

Where is BORNTORUNE AS based?

BORNTORUNE AS has its business address in Fyllingsdalen.

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

Report a problem

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