BIZTRAC BETA
Combined facilities support activities

SNØ OG UTEMILJØ AS

Org. no. 925270245 Limited company (AS) Kongsvinger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 13,000
Equity NOK 91,000
Incorporated 2020
Share capital NOK 30,000

SNØ OG UTEMILJØ AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 925270245. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Snørydding, gressklipping, diverse utomhus vedlikeholdsarbeid, støttemurbygging, samt dertil hørende virksomhet og deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 13,000
Equity
NOK 91,000
Est. value
NOK 102,000

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.4%
Weak
Equity as a share of total capital

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

Who owns SNØ OG UTEMILJØ AS?

SYNNØVE MATHAN KNIVSLAND
SNØ OG UTEMILJØ AS
NOK 1.9m rev. · NOK 13,000 profit

SNØ OG UTEMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNØ OG UTEMILJØ AS

Who owns SNØ OG UTEMILJØ AS?

SYNNØVE MATHAN KNIVSLAND is the largest registered owner, with 100.0%.

What is the revenue of SNØ OG UTEMILJØ AS?

SNØ OG UTEMILJØ AS had revenue of NOK 1.9m in 2025.

Who is the general manager of SNØ OG UTEMILJØ AS?

Knut Åge Tangen is registered as general manager of SNØ OG UTEMILJØ AS.

Where is SNØ OG UTEMILJØ AS based?

SNØ OG UTEMILJØ AS has its business address in Kongsvinger.

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.