BIZTRAC BETA
Site preparation

SÆTER OG SØNNER AS

Org. no. 913526619 Limited company (AS) Os Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 943,000
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 30,000

SÆTER OG SØNNER AS is registered as a limited company in Os, Innlandet with organisation number 913526619. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Investeringer i og utvikling av fast eiendom, kjøp og salg av landbruksrelaterte varer og tjenester, utleie av maskiner og maskinkjører, transport samt kjøp og salg av varer og tjenester som naturlig hører sammen med dette, herunder investeringer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 943,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 943,000
Equity
NOK 1.1m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns SÆTER OG SØNNER AS?

JON JARLE SÆTER
SÆTER OG SØNNER AS
NOK 2.3m rev. · NOK 943,000 profit

SÆTER OG SØNNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SÆTER OG SØNNER AS

Who owns SÆTER OG SØNNER AS?

JON JARLE SÆTER is the largest registered owner, with 100.0%.

What is the revenue of SÆTER OG SØNNER AS?

SÆTER OG SØNNER AS had revenue of NOK 2.3m in 2025.

Who is the general manager of SÆTER OG SØNNER AS?

Jon Jarle Sæter is registered as general manager of SÆTER OG SØNNER AS.

Where is SÆTER OG SØNNER AS based?

SÆTER OG SØNNER AS has its business address in Tufsingdalen.

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.