BIZTRAC BETA
Support services to forestry

FOSSLAND AS

Org. no. 989685929 Limited company (AS) Namsos Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 331,000
Equity NOK −79,000
Incorporated 2006
Share capital NOK 450,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−79k kr).

FOSSLAND AS is registered as a limited company in Namsos, Trøndelag with organisation number 989685929. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2006. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Entreprenørvirksomhet med skogsmaskiner og annen virksomhet som naturlig hører til, samt delta i andre virksomheter herunder kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 331,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 331,000
Equity
NOK −79,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FOSSLAND AS?

TARALD MONSLAUP FOSSLAND
FOSSLAND AS
NOK 4.4m rev. · NOK 331,000 profit

FOSSLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSSLAND AS

Who owns FOSSLAND AS?

TARALD MONSLAUP FOSSLAND is the largest registered owner, with 100.0%.

What is the revenue of FOSSLAND AS?

FOSSLAND AS had revenue of NOK 4.4m in 2025.

Who is the general manager of FOSSLAND AS?

Tarald Monslaup Fossland is registered as general manager of FOSSLAND AS.

Where is FOSSLAND AS based?

FOSSLAND AS has its business address in Fosslandsosen.

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.