biztrac. BETA
COMPANY REGISTER PROFILE
817720412 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

FJELLGUIDEN TYDAL AS

Org. no. 817720412 Limited company (AS) Tydal Incorporated 2016 Active
Revenue 2025 NOK 4.5m
Operating profit NOK 147,000
Equity NOK 1.1m
Incorporated 2016
Employees 15
Share capital NOK 30,000

FJELLGUIDEN TYDAL AS is registered as a limited company in Tydal, Trøndelag with organisation number 817720412. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levere tjenester innen turisme og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
▼ −32 %
Operating profit
NOK 147,000
▼ −75 %
Equity
NOK 1.1m
▲ +6 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns FJELLGUIDEN TYDAL AS?

FJELLGUIDEN TYDAL AS
NOK 4.5m rev. · NOK 147,000 profit

FJELLGUIDEN TYDAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELLGUIDEN TYDAL AS

Who owns FJELLGUIDEN TYDAL AS?

Lars Østby Nilsen is the largest registered owner, with 50.0%.

What is the revenue of FJELLGUIDEN TYDAL AS?

FJELLGUIDEN TYDAL AS had revenue of NOK 4.5m in 2025.

Where is FJELLGUIDEN TYDAL AS based?

FJELLGUIDEN TYDAL 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.