BIZTRAC BETA
Support activities for crop production

S. UTHUS ENTREPRENØR AS

Org. no. 919277319 Limited company (AS) Selbu Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 939,000
Equity NOK 3.4m
Incorporated 2017
Employees 9
Share capital NOK 150,000

S. UTHUS ENTREPRENØR AS is registered as a limited company in Selbu, Trøndelag with organisation number 919277319. The business is classified under support activities for crop production (NACE 01.610). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Entreprenør innen snøbrøyting, strøing, kantslått, kosting og vedlikehold av anlegg, samt slåing/pressing av grovfôr.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 939,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 939,000
Equity
NOK 3.4m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns S. UTHUS ENTREPRENØR AS?

STIG MORTEN UTHUS
S. UTHUS ENTREPRENØR AS
NOK 7.4m rev. · NOK 939,000 profit

S. UTHUS ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S. UTHUS ENTREPRENØR AS

Who owns S. UTHUS ENTREPRENØR AS?

STIG MORTEN UTHUS is the largest registered owner, with 100.0%.

What is the revenue of S. UTHUS ENTREPRENØR AS?

S. UTHUS ENTREPRENØR AS had revenue of NOK 7.4m in 2024.

Who is the general manager of S. UTHUS ENTREPRENØR AS?

Stig Morten Uthus is registered as general manager of S. UTHUS ENTREPRENØR AS.

Where is S. UTHUS ENTREPRENØR AS based?

S. UTHUS ENTREPRENØR AS has its business address in Selbu.

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.