BIZTRAC BETA
Other cleaning activities

FOLLO SNØ AS

Org. no. 921002998 Limited company (AS) Indre Østfold Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 919,000
Equity NOK 4.1m
Incorporated 2018
Share capital NOK 1.1m

FOLLO SNØ AS is registered as a limited company in Indre Østfold, Østfold with organisation number 921002998. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2018. Registered share capital is NOK 1.1m, divided into 100 shares. The company's stated purpose is: “Drive salg, service og reparasjon av maskiner, deler og lignende utstyr og hva som herved står i forbindelse til anlegg, industri og landbruk, delta i lignende aktiviteter som veivedlikehold, snørydding og strøing, herunder deltakelse i annen virksomhet, samt import og agenturvirksomhet. Det kan også eie og drive fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 919,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 919,000
Equity
NOK 4.1m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns FOLLO SNØ AS?

MARTIN ØDELI
FOLLO SNØ AS
NOK 5.7m rev. · NOK 919,000 profit

FOLLO SNØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOLLO SNØ AS

Who owns FOLLO SNØ AS?

MARTIN ØDELI is the largest registered owner, with 50.0%.

What is the revenue of FOLLO SNØ AS?

FOLLO SNØ AS had revenue of NOK 5.7m in 2024.

Who is the general manager of FOLLO SNØ AS?

Marius Ødeli is registered as general manager of FOLLO SNØ AS.

Where is FOLLO SNØ AS based?

FOLLO SNØ AS has its business address in Tomter.

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.