BIZTRAC BETA
Civil engineering activities

SNO PROSJEKTUTVIKLING AS

Org. no. 936167934 Limited company (AS) Hamar Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 482,000
Operating profit NOK 90,000
Equity NOK 124,000
Incorporated 2025
Share capital NOK 60,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-08-21.

SNO PROSJEKTUTVIKLING AS is registered as a limited company in Hamar, Innlandet with organisation number 936167934. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Tilby prosjektledelse og rådgivningstjenester innen boligbygging og eiendomsutvikling, samt annen virksomhet som naturlig faller sammen med dette. Selskapet kan også delta og investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 482,000 in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 482,000
Operating profit
NOK 90,000
Equity
NOK 124,000
Est. value
NOK 457,000

Financial health · 2025

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns SNO PROSJEKTUTVIKLING AS?

JUKO INVEST AS
SNO PROSJEKTUTVIKLING AS
NOK 482,000 rev. · NOK 90,000 profit

SNO PROSJEKTUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SNO PROSJEKTUTVIKLING AS

Who owns SNO PROSJEKTUTVIKLING AS?

JUKO INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of SNO PROSJEKTUTVIKLING AS?

SNO PROSJEKTUTVIKLING AS had revenue of NOK 482,000 in 2025.

Where is SNO PROSJEKTUTVIKLING AS based?

SNO PROSJEKTUTVIKLING AS has its business address in Hamar.

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.