BIZTRAC BETA
Rental and operating of own or leased real estate

BJUGNVEIEN 24 AS

Org. no. 813865262 Limited company (AS) Ørland Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.1m
Equity NOK 237,000
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BJUGNVEIEN 24 AS is registered as a limited company in Ørland, Trøndelag with organisation number 813865262. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og drift av eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.1m
Equity
NOK 237,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.8%
Not satisfactory
Equity as a share of total capital

Who owns BJUGNVEIEN 24 AS?

RÅDHUSVEIEN 20 AS
BJUGNVEIEN 24 AS
NOK 1.8m rev. · NOK 1.1m profit

BJUGNVEIEN 24 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJUGNVEIEN 24 AS

Who owns BJUGNVEIEN 24 AS?

RÅDHUSVEIEN 20 AS is the largest registered owner, with 100.0%.

What is the revenue of BJUGNVEIEN 24 AS?

BJUGNVEIEN 24 AS had revenue of NOK 1.8m in 2025.

Who is the general manager of BJUGNVEIEN 24 AS?

Kristian Solem is registered as general manager of BJUGNVEIEN 24 AS.

Where is BJUGNVEIEN 24 AS based?

BJUGNVEIEN 24 AS has its business address in Bjugn.

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.