BIZTRAC BETA
COMPANY REGISTER PROFILE
935338050 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

KØPPENVEGEN 4 AS

Org. no. 935338050 Limited company (AS) Inderøy Incorporated 2025 Active
Ownership graph ↗
Equity NOK 34,000
Incorporated 2025
Share capital NOK 40,000

KØPPENVEGEN 4 AS is registered as a limited company in Inderøy, Trøndelag with organisation number 935338050. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Utleie av lokaler.”.

Key figures · 2025

Equity
NOK 34,000
Est. value
NOK 31,000

Financial health · 2025

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

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

Who owns KØPPENVEGEN 4 AS?

KØPPENVEGEN 4 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KØPPENVEGEN 4 AS

Who owns KØPPENVEGEN 4 AS?

KNUT ARNE AASAN is the largest registered owner, with 50.0%.

Who is the general manager of KØPPENVEGEN 4 AS?

Arne Ivar Sundseth is registered as general manager of KØPPENVEGEN 4 AS.

Where is KØPPENVEGEN 4 AS based?

KØPPENVEGEN 4 AS has its business address in Mosvik.

Property

Business address Køppenvegen 4, 7690 Mosvik
Cadastral unit 5053-318/30/0/0
Building Lekepark · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.