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

STRØMMEHAVEN GLADMAT AS

Org. no. 925348678 Limited company (AS) Kristiansand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 281,000
Equity NOK 181,000
Incorporated 2020
Share capital NOK 100,000

STRØMMEHAVEN GLADMAT AS is registered as a limited company in Kristiansand, Agder with organisation number 925348678. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 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 2025 financial year, show NOK 4.0m in revenue and NOK 281,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 281,000
Equity
NOK 181,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns STRØMMEHAVEN GLADMAT AS?

TERJE ROGSTAD
STRØMMEHAVEN GLADMAT AS
NOK 4.0m rev. · NOK 281,000 profit

STRØMMEHAVEN GLADMAT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRØMMEHAVEN GLADMAT AS

Who owns STRØMMEHAVEN GLADMAT AS?

TERJE ROGSTAD is the largest registered owner, with 60.0%.

What is the revenue of STRØMMEHAVEN GLADMAT AS?

STRØMMEHAVEN GLADMAT AS had revenue of NOK 4.0m in 2025.

Who is the general manager of STRØMMEHAVEN GLADMAT AS?

Terje Rogstad is registered as general manager of STRØMMEHAVEN GLADMAT AS.

Where is STRØMMEHAVEN GLADMAT AS based?

STRØMMEHAVEN GLADMAT AS has its business address in Søgne.

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.