BIZTRAC BETA
Other captive investment companies

TUENESET AS

Org. no. 991807209 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK 96,000
Equity NOK 23.2m
Incorporated 2007
Share capital NOK 320,000

TUENESET AS is registered as a limited company in Bærum, Akershus with organisation number 991807209. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 320,000, divided into 320000 shares. The company's stated purpose is: “Handel med og investeringer i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK 96,000
Equity
NOK 23.2m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns TUENESET AS?

HILDE BRITT SKARBØVIK MELLBYE
TUENESET AS
NOK 100,000 rev. · NOK 96,000 profit

TUENESET AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TUENESET AS own?

TUENESET AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about TUENESET AS

Who owns TUENESET AS?

HILDE BRITT SKARBØVIK MELLBYE is the largest registered owner, with 96.9%.

What is the revenue of TUENESET AS?

TUENESET AS had revenue of NOK 100,000 in 2024.

Who is the general manager of TUENESET AS?

Hilde Britt Skarbøvik Mellbye is registered as general manager of TUENESET AS.

Where is TUENESET AS based?

TUENESET AS has its business address in Høvik.

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.