BIZTRAC BETA
Activities of advertising agencies

KREPSEN OG VÆREN AS

Org. no. 910773976 Limited company (AS) Bærum Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −816,000
Incorporated 1981
Share capital NOK 100,000

Signals

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

KREPSEN OG VÆREN AS is registered as a limited company in Bærum, Akershus with organisation number 910773976. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentbistand og annen tjenesteyting, deltakelse i andre selskaper, samt virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −816,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns KREPSEN OG VÆREN AS?

PETTER BRANDT
KREPSEN OG VÆREN AS
NOK 0 rev. · NOK 0 profit

KREPSEN OG VÆREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KREPSEN OG VÆREN AS

Who owns KREPSEN OG VÆREN AS?

PETTER BRANDT is the largest registered owner, with 100.0%.

What is the revenue of KREPSEN OG VÆREN AS?

KREPSEN OG VÆREN AS had revenue of NOK 0 in 2024.

Who is the general manager of KREPSEN OG VÆREN AS?

Petter Brandt is registered as general manager of KREPSEN OG VÆREN AS.

Where is KREPSEN OG VÆREN AS based?

KREPSEN OG VÆREN AS has its business address in Haslum.

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.