BIZTRAC BETA
Web search portal activities

BRYGGA I TØNSBERG AS

Org. no. 826129352 Limited company (AS) Færder Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 836,000
Operating profit NOK 54,000
Equity NOK 37,000
Incorporated 2020
Share capital NOK 30,000

BRYGGA I TØNSBERG AS is registered as a limited company in Færder, Vestfold with organisation number 826129352. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive redaksjonell virksomhet og markedsføringstjenester på nettsiden bryggaitonsberg.no og i sosiale medier.”. The most recent filed accounts, for the 2024 financial year, show NOK 836,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2024

Revenue
NOK 836,000
Operating profit
NOK 54,000
Equity
NOK 37,000
Est. value
NOK 330,000

Financial health · 2024

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

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

Who owns BRYGGA I TØNSBERG AS?

CHRISTOFFER ROBIN TILLER
BRYGGA I TØNSBERG AS
NOK 836,000 rev. · NOK 54,000 profit

BRYGGA I TØNSBERG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRYGGA I TØNSBERG AS

Who owns BRYGGA I TØNSBERG AS?

CHRISTOFFER ROBIN TILLER is the largest registered owner, with 50.0%.

What is the revenue of BRYGGA I TØNSBERG AS?

BRYGGA I TØNSBERG AS had revenue of NOK 836,000 in 2024.

Who is the general manager of BRYGGA I TØNSBERG AS?

Christoffer Robin Tiller is registered as general manager of BRYGGA I TØNSBERG AS.

Where is BRYGGA I TØNSBERG AS based?

BRYGGA I TØNSBERG AS has its business address in Nøtterøy.

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.