BIZTRAC BETA
Business and other management consultancy activities

TILLITY AS

Org. no. 926776142 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 984
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

TILLITY AS is registered as a limited company in Oslo, Oslo with organisation number 926776142. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Strategisk rådgiving for enkeltpersoner, grupper og hele organisasjoner, gjerne med utgangspunkt i formulering og implementering av ny forretningsstrategi, og støtte i følgende endringer både innenfor IT og kjernevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 984 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 984
Equity
NOK 30,000
Est. value
NOK 20,000

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.9%
Weak
Equity as a share of total capital

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

Who owns TILLITY AS?

MAX PETTER BREEN HERNER
TILLITY AS
NOK 3.4m rev. · NOK 984 profit

TILLITY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TILLITY AS

Who owns TILLITY AS?

MAX PETTER BREEN HERNER is the largest registered owner, with 100.0%.

What is the revenue of TILLITY AS?

TILLITY AS had revenue of NOK 3.4m in 2025.

Who is the general manager of TILLITY AS?

Max Petter Breen Herner is registered as general manager of TILLITY AS.

Where is TILLITY AS based?

TILLITY AS has its business address in Oslo.

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.