BIZTRAC BETA
Rental and operating of own or leased real estate

ELVEVEIEN 136 AS

Org. no. 914321085 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 486,000
Operating profit NOK 178,000
Equity NOK 9.6m
Incorporated 2014
Share capital NOK 150,000

ELVEVEIEN 136 AS is registered as a limited company in Larvik, Vestfold with organisation number 914321085. 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 150,000, divided into 30000 shares. The company's stated purpose is: “Utleie og drift av fast eiendom, kjøp og salg av fast eiendom, eiendomsutvikling, kjøp og salg av aksjer i andre selskaper, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 486,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2024

Revenue
NOK 486,000
Operating profit
NOK 178,000
Equity
NOK 9.6m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns ELVEVEIEN 136 AS?

ALBERT BØE HOLDING AS
ELVEVEIEN 136 AS
NOK 486,000 rev. · NOK 178,000 profit

ELVEVEIEN 136 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELVEVEIEN 136 AS

Who owns ELVEVEIEN 136 AS?

ALBERT BØE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ELVEVEIEN 136 AS?

ELVEVEIEN 136 AS had revenue of NOK 486,000 in 2024.

Who is the general manager of ELVEVEIEN 136 AS?

Suzanne Madelene Svärd is registered as general manager of ELVEVEIEN 136 AS.

Where is ELVEVEIEN 136 AS based?

ELVEVEIEN 136 AS has its business address in Larvik.

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.