BIZTRAC BETA
Business and other management consultancy activities

TREDJEPART AS

Org. no. 994985922 Limited company (AS) Asker Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 441,000
Equity NOK 1.1m
Incorporated 2010
Employees 5
Share capital NOK 50,000

TREDJEPART AS is registered as a limited company in Asker, Akershus with organisation number 994985922. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010 and has 5 registered employees. Registered share capital is NOK 50,000, divided into 4000 shares. The company's stated purpose is: “Salg av konsulenttjenester innen økonomi og bedriftsrådgivning og hva dermed står i forbindelse. Selskapet kan investere i og drive utleie av fast eiendom. Selskapet kan investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 441,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 441,000
Equity
NOK 1.1m
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.9%
Good
Equity as a share of total capital

Who owns TREDJEPART AS?

KRISTIAN JACOBSEN
TREDJEPART AS
NOK 8.7m rev. · NOK 441,000 profit

TREDJEPART AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TREDJEPART AS

Who owns TREDJEPART AS?

KRISTIAN JACOBSEN is the largest registered owner, with 50.0%.

What is the revenue of TREDJEPART AS?

TREDJEPART AS had revenue of NOK 8.7m in 2025.

Who is the general manager of TREDJEPART AS?

Kristian Jacobsen is registered as general manager of TREDJEPART AS.

Where is TREDJEPART AS based?

TREDJEPART AS has its business address in Billingstad.

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

Report a problem

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