BIZTRAC BETA
Other captive investment companies

LIQUEUR DE TIRAGE AS

Org. no. 916455879 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −137,000
Equity NOK 27.6m
Incorporated 2015
Share capital NOK 34,000

Signals

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

LIQUEUR DE TIRAGE AS is registered as a limited company in Stavanger, Rogaland with organisation number 916455879. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 34,000, divided into 34 shares. The company's stated purpose is: “Eie aksjer og verdipapirer i andre foretak og annen tilknyttet investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −137,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −137,000
Equity
NOK 27.6m
Est. value
NOK 19.0m

Financial health · 2025

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

Who owns LIQUEUR DE TIRAGE AS?

BØRRE HEGGERNES
LIQUEUR DE TIRAGE AS
NOK 0 rev. · NOK −137,000 profit

LIQUEUR DE TIRAGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIQUEUR DE TIRAGE AS own?

LIQUEUR DE TIRAGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIQUEUR DE TIRAGE AS

Who owns LIQUEUR DE TIRAGE AS?

BØRRE HEGGERNES is the largest registered owner, with 100.0%.

What is the revenue of LIQUEUR DE TIRAGE AS?

LIQUEUR DE TIRAGE AS had revenue of NOK 0 in 2024.

Where is LIQUEUR DE TIRAGE AS based?

LIQUEUR DE TIRAGE AS has its business address in Stavanger.

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.