biztrac. BETA
COMPANY REGISTER PROFILE
935858232 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

FLASNES HOLDING AS

Org. no. 935858232 Limited company (AS) Namsos Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 31.2m
Incorporated 2025
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

FLASNES HOLDING AS is registered as a limited company in Namsos, Trøndelag with organisation number 935858232. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, samt det som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 31.2m
Est. value
NOK 18.9m

Financial health · 2025

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

Who owns FLASNES HOLDING AS?

FLASNES HOLDING AS
NOK 0 rev. · NOK −3,000 profit

FLASNES HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLASNES HOLDING AS own?

FLASNES HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FLASNES HOLDING AS

Who owns FLASNES HOLDING AS?

Erik Flasnes is the largest registered owner, with 100.0%.

What is the revenue of FLASNES HOLDING AS?

FLASNES HOLDING AS had revenue of NOK 0 in 2025.

Where is FLASNES HOLDING AS based?

FLASNES HOLDING AS has its business address in Spillum.

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.