BIZTRAC BETA
Other captive investment companies

B. SCHØNING AS

Org. no. 922039682 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −25,000
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

B. SCHØNING AS is registered as a limited company in Tromsø, Troms with organisation number 922039682. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i eierandeler i andre selskaper samt i finansielle instrumenter, e.l. samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 30,000
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.0%
Weak
Equity as a share of total capital

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

Who owns B. SCHØNING AS?

BENTE EVJEN SCHØNING
B. SCHØNING AS
NOK 0 rev. · NOK −25,000 profit

B. SCHØNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does B. SCHØNING AS own?

B. SCHØNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about B. SCHØNING AS

Who owns B. SCHØNING AS?

BENTE EVJEN SCHØNING is the largest registered owner, with 100.0%.

What is the revenue of B. SCHØNING AS?

B. SCHØNING AS had revenue of NOK 0 in 2024.

Where is B. SCHØNING AS based?

B. SCHØNING AS has its business address in Tromsdalen.

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.