BIZTRAC BETA
Other services incidental to land transport n.e.c.

INNHERRED BILBERGING AS

Org. no. 831088192 Limited company (AS) Verdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 17,000
Equity NOK 70,000
Incorporated 2023
Share capital NOK 30,000

INNHERRED BILBERGING AS is registered as a limited company in Verdal, Trøndelag with organisation number 831088192. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive bilbergingsvirksomhet, samt det som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 17,000
Equity
NOK 70,000
Est. value
NOK 91,000

Financial health · 2025

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

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

Who owns INNHERRED BILBERGING AS?

JAN ERIK HAGA
INNHERRED BILBERGING AS
NOK 4.0m rev. · NOK 17,000 profit

INNHERRED BILBERGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNHERRED BILBERGING AS

Who owns INNHERRED BILBERGING AS?

JAN ERIK HAGA is the largest registered owner, with 100.0%.

What is the revenue of INNHERRED BILBERGING AS?

INNHERRED BILBERGING AS had revenue of NOK 4.0m in 2025.

Who is the general manager of INNHERRED BILBERGING AS?

Jan Erik Haga is registered as general manager of INNHERRED BILBERGING AS.

Where is INNHERRED BILBERGING AS based?

INNHERRED BILBERGING AS has its business address in Verdal.

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.