BIZTRAC BETA
COMPANY REGISTER PROFILE
924486899 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

TERBI AS

Org. no. 924486899 Limited company (AS) Modum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 72,000
Operating profit NOK −11,000
Equity NOK 138,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

TERBI AS is registered as a limited company in Modum, Buskerud with organisation number 924486899. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppdragsvirksomhet og konsulenttjenester innen landbruket og anlegg, samt eiendomsforvaltning og eiendomsutvikling. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 72,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 72,000
Operating profit
NOK −11,000
Equity
NOK 138,000
Est. value
NOK 143,000

Financial health · 2025

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

Who owns TERBI AS?

TORLEIF OLAV TERUM
TERBI AS
NOK 72,000 rev. · NOK −11,000 profit

TERBI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TERBI AS

Who owns TERBI AS?

TORLEIF OLAV TERUM is the largest registered owner, with 100.0%.

What is the revenue of TERBI AS?

TERBI AS had revenue of NOK 72,000 in 2025.

Where is TERBI AS based?

TERBI AS has its business address in Åmot.

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.