BIZTRAC BETA
Retail sale of information and communication equipment

TNB AMANDA AS

Org. no. 920631576 Limited company (AS) Haugesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 16.1m
Operating profit NOK 384,000
Equity NOK 684,000
Incorporated 2018
Employees 10
Share capital NOK 100,000

TNB AMANDA AS is registered as a limited company in Haugesund, Rogaland with organisation number 920631576. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Handel, agentur og konsulentvirksomhet, inkl. markedsføring og salg av mobil, data og telefonløsninger og service på dette. Selskapet kan også eie/delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.1m in revenue and NOK 384,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.1m
Operating profit
NOK 384,000
Equity
NOK 684,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns TNB AMANDA AS?

MARINIUS HANDEL AS
TNB AMANDA AS
NOK 16.1m rev. · NOK 384,000 profit

TNB AMANDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TNB AMANDA AS

Who owns TNB AMANDA AS?

MARINIUS HANDEL AS is the largest registered owner, with 100.0%.

What is the revenue of TNB AMANDA AS?

TNB AMANDA AS had revenue of NOK 16.1m in 2025.

Who is the general manager of TNB AMANDA AS?

Nikolai Marinius Foss Stray is registered as general manager of TNB AMANDA AS.

Where is TNB AMANDA AS based?

TNB AMANDA AS has its business address in Haugesund.

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.