BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

TONSTAD KOLONIAL AS

Org. no. 931054821 Limited company (AS) Sirdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 33,000
Equity NOK 584,000
Incorporated 2023
Employees 6
Share capital NOK 130,000

TONSTAD KOLONIAL AS is registered as a limited company in Sirdal, Agder with organisation number 931054821. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 130,000, divided into 1300 shares. The company's stated purpose is: “Butikkhandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 33,000
Equity
NOK 584,000
Est. value
NOK 373,000

Financial health · 2024

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

Who owns TONSTAD KOLONIAL AS?

JAN PETTER OUSDAL
TONSTAD KOLONIAL AS
NOK 10.5m rev. · NOK 33,000 profit

TONSTAD KOLONIAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TONSTAD KOLONIAL AS

Who owns TONSTAD KOLONIAL AS?

JAN PETTER OUSDAL is the largest registered owner, with 50.0%.

What is the revenue of TONSTAD KOLONIAL AS?

TONSTAD KOLONIAL AS had revenue of NOK 10.5m in 2024.

Who is the general manager of TONSTAD KOLONIAL AS?

May-Bente Bjørnestad is registered as general manager of TONSTAD KOLONIAL AS.

Where is TONSTAD KOLONIAL AS based?

TONSTAD KOLONIAL AS has its business address in Tonstad.

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.