BIZTRAC BETA
COMPANY REGISTER PROFILE
988875465 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

TARIFA AS

Org. no. 988875465 Limited company (AS) Asker Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −32,000
Equity NOK 19.0m
Incorporated 2005
Share capital NOK 108,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

TARIFA AS is registered as a limited company in Asker, Akershus with organisation number 988875465. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 108,000, divided into 36040 shares. The company's stated purpose is: “Handel, megling, agenturvirksomhet og investering i aksjer, verdipapirer og fast eiendom, samt alt hva dermed står i forbindelse. ”.

Key figures · 2025

Operating profit
NOK −32,000
Equity
NOK 19.0m
Est. value
NOK 15.9m

Financial health · 2025

Liquidity
87.78
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
98.9%
Very good
Equity as a share of total capital

Who owns TARIFA AS?

TARIFA AS
· NOK −32,000 profit

TARIFA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TARIFA AS

Who owns TARIFA AS?

TOR KVEIM is the largest registered owner, with 100.0%.

Where is TARIFA AS based?

TARIFA AS has its business address in Nesbru.

Property

Business address Sonja Henies vei 1, 1394 Nesbru
Cadastral unit 3203-39/1799/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.