BIZTRAC BETA
Rental and operating of own or leased real estate

HITRA BO-TILBUD AS

Org. no. 930149721 Limited company (AS) Hitra Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK 1.9m
Equity NOK 19.0m
Incorporated 1976
Share capital NOK 326,000

HITRA BO-TILBUD AS is registered as a limited company in Hitra, Trøndelag with organisation number 930149721. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1976. Registered share capital is NOK 326,000, divided into 3832 shares. The company's stated purpose is: “Administrasjon og utleie av egne hybel-, kontor- og forretningsbygg, kjøp og salg av eiendommer, deltakelse i andre selskaper med samme formål, og hva som forøvrig står i forbindelse med disse virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK 1.9m
Equity
NOK 19.0m
Est. value
NOK 16.1m

Financial health · 2024

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

Who owns HITRA BO-TILBUD AS?

VABE HOLDING AS
HITRA BO-TILBUD AS
NOK 4.0m rev. · NOK 1.9m profit

HITRA BO-TILBUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HITRA BO-TILBUD AS

Who owns HITRA BO-TILBUD AS?

VABE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HITRA BO-TILBUD AS?

HITRA BO-TILBUD AS had revenue of NOK 4.0m in 2024.

Who is the general manager of HITRA BO-TILBUD AS?

Stig Eirik Bremnes is registered as general manager of HITRA BO-TILBUD AS.

Where is HITRA BO-TILBUD AS based?

HITRA BO-TILBUD AS has its business address in Hitra.

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.