BIZTRAC BETA
Retail sale of information and communication equipment

TELEKIOSKEN BRYN AS

Org. no. 932166119 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK −89,000
Equity NOK 7,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−89k kr).

TELEKIOSKEN BRYN AS is registered as a limited company in Oslo, Oslo with organisation number 932166119. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Butikkhandel med telekommunikasjonsutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK −89,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK −89,000
Equity
NOK 7,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.5%
Weak
Equity as a share of total capital

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

Who owns TELEKIOSKEN BRYN AS?

SÅ&HØSTE AS
TELEKIOSKEN BRYN AS
NOK 6.1m rev. · NOK −89,000 profit

TELEKIOSKEN BRYN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TELEKIOSKEN BRYN AS

Who owns TELEKIOSKEN BRYN AS?

SÅ&HØSTE AS is the largest registered owner, with 100.0%.

What is the revenue of TELEKIOSKEN BRYN AS?

TELEKIOSKEN BRYN AS had revenue of NOK 6.1m in 2024.

Who is the general manager of TELEKIOSKEN BRYN AS?

Roy Malterud is registered as general manager of TELEKIOSKEN BRYN AS.

Where is TELEKIOSKEN BRYN AS based?

TELEKIOSKEN BRYN AS has its business address in Oslo.

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.