BIZTRAC BETA
Activities of excursion and event organisers

BORGLEDEN PILEGRIMSSENTER AS

Org. no. 926572725 Limited company (AS) Sarpsborg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 84,000
Equity NOK 352,000
Incorporated 2020
Share capital NOK 50,000

BORGLEDEN PILEGRIMSSENTER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 926572725. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Selskapet skal utvikle pilegrimsleden Borgleden til lokal verdiskaping og fremme aktivitet for næringsliv, museer, kultur, kirke, kulturminner samt offentlig og frivillig virksomhet i regionen.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 84,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 84,000
Equity
NOK 352,000
Est. value
NOK 563,000

Financial health · 2025

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

Who owns BORGLEDEN PILEGRIMSSENTER AS?

No shareholders are registered for BORGLEDEN PILEGRIMSSENTER AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BORGLEDEN PILEGRIMSSENTER AS

What is the revenue of BORGLEDEN PILEGRIMSSENTER AS?

BORGLEDEN PILEGRIMSSENTER AS had revenue of NOK 1.0m in 2025.

Who is the general manager of BORGLEDEN PILEGRIMSSENTER AS?

Line Kjølberg is registered as general manager of BORGLEDEN PILEGRIMSSENTER AS.

Where is BORGLEDEN PILEGRIMSSENTER AS based?

BORGLEDEN PILEGRIMSSENTER AS has its business address in Sarpsborg.

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.