BIZTRAC BETA
Wired, wireless, and satellite telecommunication activities

ERVIKVEIEN 70 B AS

Org. no. 990696241 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 355,000
Operating profit NOK 225,000
Equity NOK 436,000
Incorporated 2006
Share capital NOK 100,000

ERVIKVEIEN 70 B AS is registered as a limited company in Bergen, Vestland with organisation number 990696241. The business is classified under wired, wireless, and satellite telecommunication activities (NACE 61.100). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive utleie av eiendom, samt alt annet som har naturlig sammenheng med dette, herunder deltagelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 355,000 in revenue and NOK 225,000 in operating profit.

Key figures · 2025

Revenue
NOK 355,000
Operating profit
NOK 225,000
Equity
NOK 436,000
Est. value
NOK 796,000

Financial health · 2025

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

Who owns ERVIKVEIEN 70 B AS?

SERAM IKT AS
ERVIKVEIEN 70 B AS
NOK 355,000 rev. · NOK 225,000 profit

ERVIKVEIEN 70 B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERVIKVEIEN 70 B AS

Who owns ERVIKVEIEN 70 B AS?

SERAM IKT AS is the largest registered owner, with 100.0%.

What is the revenue of ERVIKVEIEN 70 B AS?

ERVIKVEIEN 70 B AS had revenue of NOK 355,000 in 2025.

Who is the general manager of ERVIKVEIEN 70 B AS?

Svein Kenneth Kaland is registered as general manager of ERVIKVEIEN 70 B AS.

Where is ERVIKVEIEN 70 B AS based?

ERVIKVEIEN 70 B AS has its business address in Øvre Ervik.

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.