BIZTRAC BETA
Operation of sports facilities

PULSPADEL STJØRDAL AS

Org. no. 988613991 Limited company (AS) Stjørdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK 452,000
Incorporated 2005
Share capital NOK 30,000

Signals

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

PULSPADEL STJØRDAL AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 988613991. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Drive med utleie av idrettsbaner, event og konferanse, kjøp og salg av idrettsutstyr, kiosksalg og dertil relatert virksomhet. Formålet innebefatter det som naturlig står i forbindelse med dette, herunder investeringer i tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 452,000
Est. value
NOK 565,000

Financial health · 2024

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

Who owns PULSPADEL STJØRDAL AS?

PULSPADEL AS
PULSPADEL STJØRDAL AS
NOK 0 rev. · NOK −19,000 profit

PULSPADEL STJØRDAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PULSPADEL STJØRDAL AS

Who owns PULSPADEL STJØRDAL AS?

PULSPADEL AS is the largest registered owner, with 50.0%.

What is the revenue of PULSPADEL STJØRDAL AS?

PULSPADEL STJØRDAL AS had revenue of NOK 0 in 2024.

Where is PULSPADEL STJØRDAL AS based?

PULSPADEL STJØRDAL AS has its business address in Stjørdal.

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.