BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

LIE SPORTSTOURNEMENTS AS

Org. no. 915684475 Limited company (AS) Haugesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 475,000
Equity NOK 124,000
Incorporated 2015
Share capital NOK 30,000

LIE SPORTSTOURNEMENTS AS is registered as a limited company in Haugesund, Rogaland with organisation number 915684475. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Markedsføring av sportsarrangementer samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 475,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 475,000
Equity
NOK 124,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.4%
Good
Equity as a share of total capital

Who owns LIE SPORTSTOURNEMENTS AS?

KARL OTTO LIE
LIE SPORTSTOURNEMENTS AS
NOK 1.6m rev. · NOK 475,000 profit

LIE SPORTSTOURNEMENTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIE SPORTSTOURNEMENTS AS

Who owns LIE SPORTSTOURNEMENTS AS?

KARL OTTO LIE is the largest registered owner, with 100.0%.

What is the revenue of LIE SPORTSTOURNEMENTS AS?

LIE SPORTSTOURNEMENTS AS had revenue of NOK 1.6m in 2025.

Who is the general manager of LIE SPORTSTOURNEMENTS AS?

Karl Otto Lie is registered as general manager of LIE SPORTSTOURNEMENTS AS.

Where is LIE SPORTSTOURNEMENTS AS based?

LIE SPORTSTOURNEMENTS AS has its business address in Haugesund.

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.