BIZTRAC BETA
Business and other management consultancy activities

SA-HO AS

Org. no. 919154810 Limited company (AS) Midt-Telemark Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 38,000
Equity NOK 62,000
Incorporated 2017
Share capital NOK 30,000

SA-HO AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 919154810. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Prosjektledelse og rådgivning innenfor nærings-, steds- og arrangementutvikling, samt alt som naturlig står i forbindelse med dette. Derunder investeringer og deltagelse i andre selskaper. Selskapets faglige ankerfeste springer ut i fra idrett- og kulturfagene.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 38,000
Equity
NOK 62,000
Est. value
NOK 203,000

Financial health · 2025

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

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

Who owns SA-HO AS?

MARIT SVALASTOG
SA-HO AS
NOK 1.4m rev. · NOK 38,000 profit

SA-HO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SA-HO AS

Who owns SA-HO AS?

MARIT SVALASTOG is the largest registered owner, with 100.0%.

What is the revenue of SA-HO AS?

SA-HO AS had revenue of NOK 1.4m in 2025.

Who is the general manager of SA-HO AS?

Marit Svalastog is registered as general manager of SA-HO AS.

Where is SA-HO AS based?

SA-HO AS has its business address in Gvarv.

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.