biztrac. BETA
COMPANY REGISTER PROFILE
930869805 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

NORDFJORD SKOGSERVICE AS

Org. no. 930869805 Limited company (AS) Gloppen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 316,000
Equity NOK 796,000
Incorporated 2023
Share capital NOK 30,000

NORDFJORD SKOGSERVICE AS is registered as a limited company in Gloppen, Vestland with organisation number 930869805. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Arbeid innen skogbrukstjenester, maskiner og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 316,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
▲ +21 %
Operating profit
NOK 316,000
▲ +44 %
Equity
NOK 796,000
▲ +44 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
3.27
Very good
Current assets ÷ current liabilities
Profitability
26.5%
Very good
Return on total assets
Solidity
72.8%
Very good
Equity as a share of total capital

Who owns NORDFJORD SKOGSERVICE AS?

NORDFJORD SKOGSERVICE AS
NOK 5.0m rev. · NOK 316,000 profit

NORDFJORD SKOGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDFJORD SKOGSERVICE AS

Who owns NORDFJORD SKOGSERVICE AS?

Sebastian Skinlo is the largest registered owner, with 100.0%.

What is the revenue of NORDFJORD SKOGSERVICE AS?

NORDFJORD SKOGSERVICE AS had revenue of NOK 5.0m in 2025.

Who is the general manager of NORDFJORD SKOGSERVICE AS?

Sebastian Skinlo is registered as general manager of NORDFJORD SKOGSERVICE AS.

Where is NORDFJORD SKOGSERVICE AS based?

NORDFJORD SKOGSERVICE AS has its business address in Breim.

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.