biztrac. BETA
COMPANY REGISTER PROFILE
915509657 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Public relations and communication activities

TEATIME TEXT AS

Org. no. 915509657 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 317,000
Operating profit NOK 134,000
Equity NOK 390,000
Incorporated 2015
Share capital NOK 36,000

TEATIME TEXT AS is registered as a limited company in Asker, Akershus with organisation number 915509657. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2015. Registered share capital is NOK 36,000, divided into 120 shares. The company's stated purpose is: “Tilby redaksjonelle tjenester for næringslivet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 317,000 in revenue and NOK 134,000 in operating profit.

Key figures · 2025

Revenue
NOK 317,000
▲ +20 %
Operating profit
NOK 134,000
▲ +101 %
Equity
NOK 390,000
▲ +1 %
Est. value
NOK 542,000

Financial health · 2025

Liquidity
3.65
Very good
Current assets ÷ current liabilities
Profitability
27.1%
Very good
Return on total assets
Solidity
72.6%
Very good
Equity as a share of total capital

Who owns TEATIME TEXT AS?

TEATIME TEXT AS
NOK 317,000 rev. · NOK 134,000 profit

TEATIME TEXT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEATIME TEXT AS

Who owns TEATIME TEXT AS?

Annette Von Haffenbrädl Münch is the largest registered owner, with 100.0%.

What is the revenue of TEATIME TEXT AS?

TEATIME TEXT AS had revenue of NOK 317,000 in 2025.

Who is the general manager of TEATIME TEXT AS?

Annette Von Haffenbrädl Münch is registered as general manager of TEATIME TEXT AS.

Where is TEATIME TEXT AS based?

TEATIME TEXT AS has its business address in Nesbru.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.