BIZTRAC BETA
Activities of advertising agencies

GBBT AS

Org. no. 997265025 Limited company (AS) Asker Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 443,000
Operating profit NOK 59,000
Equity NOK 158,000
Incorporated 2011
Share capital NOK 30,000

GBBT AS is registered as a limited company in Asker, Akershus with organisation number 997265025. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2011. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Konsulentvirksomhet og investeringer og andre produkter/tjenester som naturlig hører sammen med dette herunder å delta i andre selskaper med lignende virksomhet og kjøp og salg eller på annen måte gjøre seg interessert i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 443,000 in revenue and NOK 59,000 in operating profit.

Key figures · 2025

Revenue
NOK 443,000
Operating profit
NOK 59,000
Equity
NOK 158,000
Est. value
NOK 372,000

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.0%
Very good
Equity as a share of total capital

Who owns GBBT AS?

JOHN TANKE SVILAND
GBBT AS
NOK 443,000 rev. · NOK 59,000 profit

GBBT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GBBT AS own?

GBBT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GBBT AS

Who owns GBBT AS?

JOHN TANKE SVILAND is the largest registered owner, with 100.0%.

What is the revenue of GBBT AS?

GBBT AS had revenue of NOK 443,000 in 2025.

Who is the general manager of GBBT AS?

John Tanke Sviland is registered as general manager of GBBT AS.

Where is GBBT AS based?

GBBT AS has its business address in Asker.

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.