BIZTRAC BETA
COMPANY REGISTER PROFILE
935502179 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TF2NULL AS

Org. no. 935502179 Limited company (AS) Asker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 44,000
Incorporated 2025
Share capital NOK 50,000

TF2NULL AS is registered as a limited company in Asker, Akershus with organisation number 935502179. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Rådgivning, kommunikasjon og grafisk design.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 44,000
Est. value
NOK 51,000

Financial health · 2025

Liquidity
7.69
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.0%
Weak
Equity as a share of total capital

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

Who owns TF2NULL AS?

TF2NULL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TF2NULL AS

Who owns TF2NULL AS?

BJØRN ALAN TAKLE FRIIS is the largest registered owner, with 50.0%.

What is the revenue of TF2NULL AS?

TF2NULL AS had revenue of NOK 0 in 2025.

Where is TF2NULL AS based?

TF2NULL AS has its business address in Asker.

Property

Business address Ringveien 37F, 1386 Asker
Cadastral unit 3203-61/792/0/0
Building Enebolig · 1 unit

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.