BIZTRAC BETA
COMPANY REGISTER PROFILE
930532878 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of other new goods

TELLEVIK CONSULTING

Org. no. 930532878 Sole proprietorship (ENK) Bergen Active
Ownership graph ↗
Revenue 2023 NOK 218,000
Operating profit NOK −33,000
Equity NOK 0

Signals

1 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−33k kr).

TELLEVIK CONSULTING is registered as a sole proprietorship in Bergen, Vestland with organisation number 930532878. The business is classified under retail sale of other new goods (NACE 47.780). The most recent filed accounts, for the 2023 financial year, show NOK 218,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2023

Revenue
NOK 218,000
Operating profit
NOK −33,000
Equity
NOK 0

Financial health · 2023

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

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

Who owns TELLEVIK CONSULTING?

No shareholders are registered for TELLEVIK CONSULTING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TELLEVIK CONSULTING

What is the revenue of TELLEVIK CONSULTING?

TELLEVIK CONSULTING had revenue of NOK 218,000 in 2023.

Where is TELLEVIK CONSULTING based?

TELLEVIK CONSULTING has its business address in Nesttun.

Property

Business address Leilighet 6 Vestre Vallavegen 1, 5227 Nesttun
Cadastral unit 4601-49/106/0/0
Building Stort frittliggende boligbygg på 2 etg · 6 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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