BIZTRAC BETA
Other captive investment companies

SAUSNEBB KAPITAL AS

Org. no. 915374204 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 4.1m
Incorporated 2015
Share capital NOK 70,000

Signals

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

SAUSNEBB KAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 915374204. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 70,000, divided into 10000 shares. The company's stated purpose is: “Handel med aksjer, obligasjoner, andre verdipapirer og andre finansinstrumenter og hva naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 4.1m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns SAUSNEBB KAPITAL AS?

EIVIND BLOMHOLM GAUSLAND
SAUSNEBB KAPITAL AS
NOK 0 rev. · NOK −8,000 profit

SAUSNEBB KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAUSNEBB KAPITAL AS own?

SAUSNEBB KAPITAL AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about SAUSNEBB KAPITAL AS

Who owns SAUSNEBB KAPITAL AS?

EIVIND BLOMHOLM GAUSLAND is the largest registered owner, with 100.0%.

What is the revenue of SAUSNEBB KAPITAL AS?

SAUSNEBB KAPITAL AS had revenue of NOK 0 in 2025.

Where is SAUSNEBB KAPITAL AS based?

SAUSNEBB KAPITAL AS has its business address in Oslo.

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.