BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

TEABAG AS

Org. no. 917686939 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 651,000
Operating profit NOK −96,000
Equity NOK 86,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−96k kr).

TEABAG AS is registered as a limited company in Bærum, Akershus with organisation number 917686939. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester og styreverv, samt investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 651,000 in revenue and NOK −96,000 in operating profit.

Key figures · 2025

Revenue
NOK 651,000
Operating profit
NOK −96,000
Equity
NOK 86,000
Est. value
NOK 253,000

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.5%
Weak
Equity as a share of total capital

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

Who owns TEABAG AS?

THOMAS GRYS
TEABAG AS
NOK 651,000 rev. · NOK −96,000 profit

TEABAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEABAG AS

Who owns TEABAG AS?

THOMAS GRYS is the largest registered owner, with 100.0%.

What is the revenue of TEABAG AS?

TEABAG AS had revenue of NOK 651,000 in 2025.

Where is TEABAG AS based?

TEABAG AS has its business address in Blommenholm.

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.