BIZTRAC BETA
Uoppgitt

ANDEBUVEIEN 63 AS

Org. no. 995739011 Limited company (AS) Færder Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 534
Equity NOK −123,000
Incorporated 2010
Share capital NOK 34,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−123k kr).

ANDEBUVEIEN 63 AS is registered as a limited company in Færder, Vestfold with organisation number 995739011. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2010. Registered share capital is NOK 34,000, divided into 100000 shares. The company's stated purpose is: “Investering i andre selskaper, kjøp, salg og utleie av fast eiendom og andre driftsmidler, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 534 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 534
Equity
NOK −123,000
Est. value
NOK 3,000

Financial health · 2025

Liquidity
110.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.1%
Weak
Equity as a share of total capital

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

Who owns ANDEBUVEIEN 63 AS?

JOAKIM ANDRE VÆTHE-LARSEN
ANDEBUVEIEN 63 AS
NOK 2.8m rev. · NOK 534 profit

ANDEBUVEIEN 63 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ANDEBUVEIEN 63 AS own?

ANDEBUVEIEN 63 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ANDEBUVEIEN 63 AS

Who owns ANDEBUVEIEN 63 AS?

JOAKIM ANDRE VÆTHE-LARSEN is the largest registered owner, with 100.0%.

What is the revenue of ANDEBUVEIEN 63 AS?

ANDEBUVEIEN 63 AS had revenue of NOK 2.8m in 2025.

Where is ANDEBUVEIEN 63 AS based?

ANDEBUVEIEN 63 AS has its business address in Vestskogen.

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.