biztrac. BETA
COMPANY REGISTER PROFILE
913290348 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

VELØYVEIEN 1 AS

Org. no. 913290348 Limited company (AS) Sandefjord Incorporated 2014 Active
Revenue 2025 NOK 751,000
Operating profit NOK 293,000
Equity NOK 1.7m
Incorporated 2014
Share capital NOK 100,000

VELØYVEIEN 1 AS is registered as a limited company in Sandefjord, Vestfold with organisation number 913290348. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom samt alt som hører naturlig til dette. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 751,000 in revenue and NOK 293,000 in operating profit.

Key figures · 2025

Revenue
NOK 751,000
▼ −12 %
Operating profit
NOK 293,000
▼ −44 %
Equity
NOK 1.7m
▲ +10 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
3.35
Very good
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
55.6%
Very good
Equity as a share of total capital

Who owns VELØYVEIEN 1 AS?

VELØYVEIEN 1 AS
NOK 751,000 rev. · NOK 293,000 profit

VELØYVEIEN 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VELØYVEIEN 1 AS

Who owns VELØYVEIEN 1 AS?

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

What is the revenue of VELØYVEIEN 1 AS?

VELØYVEIEN 1 AS had revenue of NOK 751,000 in 2025.

Who is the general manager of VELØYVEIEN 1 AS?

Thomas Richard Rogstad is registered as general manager of VELØYVEIEN 1 AS.

Where is VELØYVEIEN 1 AS based?

VELØYVEIEN 1 AS has its business address in Sandefjord.

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

Report a problem

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