BIZTRAC BETA
Graphic design and visual communication activities

FROZT REKLAME AS

Org. no. 911852500 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 153,000
Operating profit NOK −754
Equity NOK 84,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−754 kr).

FROZT REKLAME AS is registered as a limited company in Oslo, Oslo with organisation number 911852500. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Grafiske designløsninger, samt alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 153,000 in revenue and NOK −754 in operating profit.

Key figures · 2025

Revenue
NOK 153,000
Operating profit
NOK −754
Equity
NOK 84,000
Est. value
NOK 121,000

Financial health · 2025

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

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

Who owns FROZT REKLAME AS?

ANN KARIN ERIKSEN
FROZT REKLAME AS
NOK 153,000 rev. · NOK −754 profit

FROZT REKLAME AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FROZT REKLAME AS

Who owns FROZT REKLAME AS?

ANN KARIN ERIKSEN is the largest registered owner, with 50.0%.

What is the revenue of FROZT REKLAME AS?

FROZT REKLAME AS had revenue of NOK 153,000 in 2025.

Who is the general manager of FROZT REKLAME AS?

Ann Karin Eriksen is registered as general manager of FROZT REKLAME AS.

Where is FROZT REKLAME AS based?

FROZT REKLAME AS has its business address in Oslo.

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.