BIZTRAC BETA
COMPANY REGISTER PROFILE
982838185 ORG. NO. 2019 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other educational support services n.e.c.

BJERKENE ROY TINNES

Org. no. 982838185 Sole proprietorship (ENK) Bamble Active
Ownership graph ↗
Revenue 2019 NOK 33,000
Operating profit NOK 14,000
Equity NOK 0

BJERKENE ROY TINNES is registered as a sole proprietorship in Bamble, Telemark with organisation number 982838185. The business is classified under other educational support services n.e.c. (NACE 85.699). The most recent filed accounts, for the 2019 financial year, show NOK 33,000 in revenue and NOK 14,000 in operating profit.

Former names: BJERKENE MEDIAPARTNER Roy Bjurholt

Key figures · 2019

Revenue
NOK 33,000
Operating profit
NOK 14,000
Equity
NOK 0
Est. value
NOK 76,000

Financial health · 2019

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 BJERKENE ROY TINNES?

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

Frequently asked questions about BJERKENE ROY TINNES

What is the revenue of BJERKENE ROY TINNES?

BJERKENE ROY TINNES had revenue of NOK 33,000 in 2019.

Where is BJERKENE ROY TINNES based?

BJERKENE ROY TINNES has its business address in Stathelle.

Property

Business address Hjortetråkket 14, 3962 Stathelle
Cadastral unit 4012-21/28/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

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.