biztrac. BETA
COMPANY REGISTER PROFILE
819002312 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TBN VIKEN AS

Org. no. 819002312 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 1.5m
Equity NOK 12.3m
Incorporated 2017
Share capital NOK 6.3m

TBN VIKEN AS is registered as a limited company in Bergen, Vestland with organisation number 819002312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 6.3m, divided into 1000 shares. The company's stated purpose is: “Erverve, oppføre eller leie og drive fast eiendommer, samt kjøp og salg av aksjer og andeler i andre selskaper med tilsvarende formål og det som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 1.5m in operating profit.

Former names: NIE VIKEN AS

Key figures · 2025

Revenue
NOK 2.3m
▲ +2 %
Operating profit
NOK 1.5m
▲ +2 %
Equity
NOK 12.3m
▲ +11 %
Est. value
NOK 10.9m

Financial health · 2025

Liquidity
16.75
Very good
Current assets ÷ current liabilities
Profitability
5.6%
Weak
Return on total assets
Solidity
45.2%
Very good
Equity as a share of total capital

Who owns TBN VIKEN AS?

TBN VIKEN AS
NOK 2.3m rev. · NOK 1.5m profit

TBN VIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TBN VIKEN AS

Who owns TBN VIKEN AS?

T. BRYNJULFSEN AS is the largest registered owner, with 100.0%.

What is the revenue of TBN VIKEN AS?

TBN VIKEN AS had revenue of NOK 2.3m in 2025.

Who is the general manager of TBN VIKEN AS?

Tore Brynjulfsen is registered as general manager of TBN VIKEN AS.

Where is TBN VIKEN AS based?

TBN VIKEN AS has its business address in Bergen.

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.