BIZTRAC BETA
Operation of arts facilities and sites

PROTIL AS

Org. no. 994576097 Limited company (AS) Bodø Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 91,000
Equity NOK −40,000
Incorporated 2009
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−40k kr).

PROTIL AS is registered as a limited company in Bodø, Nordland with organisation number 994576097. The business is classified under operation of arts facilities and sites (NACE 90.310). The company was incorporated in 2009. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Selskapets virksomhet er investering i andre selskaper, samt musikk og lydtekniske tjenester i forbindelse med konserter og annen virksomhet som trenger lydteknisk bistand.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 91,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 91,000
Equity
NOK −40,000
Est. value
NOK 819,000

Financial health · 2024

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.3%
Weak
Equity as a share of total capital

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

Who owns PROTIL AS?

THOR-IVAR LUND
PROTIL AS
NOK 1.2m rev. · NOK 91,000 profit

PROTIL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PROTIL AS own?

PROTIL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PROTIL AS

Who owns PROTIL AS?

THOR-IVAR LUND is the largest registered owner, with 100.0%.

What is the revenue of PROTIL AS?

PROTIL AS had revenue of NOK 1.2m in 2024.

Where is PROTIL AS based?

PROTIL AS has its business address in Bodø.

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.