BIZTRAC BETA
Hotels and similar accommodation

KIRKVOLLEN PILEGRIMSGÅRD AS

Org. no. 918710051 Limited company (AS) Tydal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 286,000
Operating profit NOK 5,000
Equity NOK 323,000
Incorporated 2017
Share capital NOK 1.6m

KIRKVOLLEN PILEGRIMSGÅRD AS is registered as a limited company in Tydal, Trøndelag with organisation number 918710051. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2017. Registered share capital is NOK 1.6m, divided into 6 shares. The company's stated purpose is: “Pilegrimsvandringer, overnattinger, matservering og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 286,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 286,000
Operating profit
NOK 5,000
Equity
NOK 323,000
Est. value
NOK 195,000

Financial health · 2024

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

Who owns KIRKVOLLEN PILEGRIMSGÅRD AS?

INGEBRIGT KIRKVOLD
KIRKVOLLEN PILEGRIMSGÅRD AS
NOK 286,000 rev. · NOK 5,000 profit

KIRKVOLLEN PILEGRIMSGÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIRKVOLLEN PILEGRIMSGÅRD AS

Who owns KIRKVOLLEN PILEGRIMSGÅRD AS?

INGEBRIGT KIRKVOLD is the largest registered owner, with 50.0%.

What is the revenue of KIRKVOLLEN PILEGRIMSGÅRD AS?

KIRKVOLLEN PILEGRIMSGÅRD AS had revenue of NOK 286,000 in 2025.

Who is the general manager of KIRKVOLLEN PILEGRIMSGÅRD AS?

Hilde Ragnfrid Kirkvold is registered as general manager of KIRKVOLLEN PILEGRIMSGÅRD AS.

Where is KIRKVOLLEN PILEGRIMSGÅRD AS based?

KIRKVOLLEN PILEGRIMSGÅRD AS has its business address in Tydal.

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.